openstack team mailing list archive
Mailing list archive
Re: Configuration of Grizzly
As I reviewed the configuration of Heat is complicated as itself, since it's ultimate for creation of "instances, floating ips, volumes, security groups, users, etc", I thought there will be a template only for instances, something simpler. But, ok, I can proceed without it.
When I create an instance, there is no private IP allocated to it, though it should be, so that optionally I can attach public IP then.
So when I create an instance in Horizon, it has always status - ERROR, IP address is empty. When I associate floating IP, it associates, but when I choose Port to be associated, it has something like: "None: 10.5.5.4". (It is private IP). But it has to be an ID of an instance instead of this "None".
The status of this address is DOWN. That is the reason I guess, but what do I need to do, I don't know.
Thank you very very much for your responses.
14.07.2013, 15:33, "Robert Collins" <robertc@xxxxxxxxxxxxxxxxx>:
> On 14 July 2013 23:30, comiqadze <comiq@xxxxxxxxx> wrote:
>> Hi everybody!
>> 1) AFAIK, for creating an instance there should be a kind of "template", which contains settings for instance, like what volume to attach, what ip address, what image to use, etc. So that when creating an instance you don't have to configure it for every instance. Is there any in Openstack?
>> As I've read in documentation, Config Drive has this function, right? In such case, is it stabilized? Is it suitable for Grizzly?
> You could use heat for that. Config Drive is just an alternative to
> the metadata service.
>> 2) My instances aren't associated with any private IPs, that are in the private network pool of addresses, and I cannot find the trace of the mistake. So what could be the possible reasons? I used GRE tunneling.
> What do you mean by point 2)? Specifically?
> Robert Collins <rbtcollins@xxxxxx>
> Distinguished Technologist
> HP Cloud Services