Re: [Openstack-operators] Ocata provider network issue failing to raise interfaces

[Matthew Czajka]

Oh hey there Curtis!

> Basically I expect there is no dhcp service. Double check the network has
dhcp?

There's DHCP running on the net nodes, but the dhcp logs don't show any
errors or warnings

In the DHCP logs, the only difference I can see is when booting from
provider it says its building the host file in /var/lib/neutron/dhcp/ while
booting from a self-service network, it says building in /var/lib/neutron/.

I have enable_isolated_metadata = True in the dhcp config.  But I noticed
that the dnsmasq logs dont show a DHCPDISCOVER or OFFER for the provider IP
I try to boot with. It shows for a self-service network.

> You could test with a config drive if you wanted to verify, or don't want
dhcp service.

I don't want to use config drive since ceph is the backend, it might mess
up instance migrations I believe?

Thanks,
Matt


On Fri, Oct 20, 2017 at 2:09 PM, Curtis <serverasc...@gmail.com> wrote:

> On Thu, Oct 19, 2017 at 5:22 PM, Matthew Czajka <mattcza...@gmail.com>
> wrote:
> > Hi All,
> >
> >
> >
> > I’m running into an issue with a new Ocata deployment. I’m unable to
> boot an
> > instance directly from the provider network. Instance logs show that it
> > keeps repeating “failed to raise interfaces” so it doesn’t get an IP
> > assigned, and then can’t reach the metatdata servers.
> >
> >
> >
> > Booting an instance from a self-service network works fine, can ping
> other
> > internal IPs within the vlan, and can assign and use a floating IP.
> >
> >
> >
> > Deployment is running linux bridge, with a flat network for provider. 3
> > controllers, 3 network nodes, and 2 compute nodes. Using dhcpdump I can
> see
> > DHCP requests being made, but no acknowledgement afterwards. If I console
> > into the server and assign the public IP statically, that IP then works.
> > It’s only at boot (or reboot), that the instance can’t grab the IP.
> >
> >
> >
> > Any help would be appreciated, I’ve been banging my head over this for a
> > while.
>
> Hey Matt :),
>
> To get metadata there has to be a dhcp server or router configured, or
> use config drive. Presumably there is no dhcp service running via
> neutron in your situation, so it can't get an IP nor the metadata
> route injected. You could test with a config drive if you wanted to
> verify, or don't want dhcp service. Sometimes organizations refuse
> dhcp services on networks, but I'm guessing that is not the case in
> this situation.
>
> Basically I expect there is no dhcp service. Double check the network has
> dhcp?
>
> Thanks,
> Curtis.
>
> >
> >
> >
> > Thanks,
> >
> > Matt C
> >
> >
> > ___
> > OpenStack-operators mailing list
> > OpenStack-operators@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> >
>
>
>
> --
> Blog: serverascode.com
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Ocata provider network issue failing to raise interfaces

[Matthew Czajka]

Hi All,



I’m running into an issue with a new Ocata deployment. I’m unable to boot
an instance directly from the provider network. Instance logs show that it
keeps repeating “failed to raise interfaces” so it doesn’t get an IP
assigned, and then can’t reach the metatdata servers.



Booting an instance from a self-service network works fine, can ping other
internal IPs within the vlan, and can assign and use a floating IP.



Deployment is running linux bridge, with a flat network for provider. 3
controllers, 3 network nodes, and 2 compute nodes. Using dhcpdump I can see
DHCP requests being made, but no acknowledgement afterwards. If I console
into the server and assign the public IP statically, that IP then works.
It’s only at boot (or reboot), that the instance can’t grab the IP.



Any help would be appreciated, I’ve been banging my head over this for a
while.



Thanks,

Matt C
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [publicClouds-wg] Public Cloud Working Group

[Matthew Czajka]

I as well would be pretty interested

-Matt

On 2016-11-15, 7:41 AM, "Tobias Schön"  wrote:

>This sounds very interesting indeed, i'll join up on that aswell!
>
>//Tobias
>
>-Ursprungligt meddelande-
>Från: Mohammed Naser [mailto:mna...@vexxhost.com]
>Skickat: den 15 november 2016 16:30
>Till: m...@mattjarvis.org.uk
>Kopia: OpenStack Operators; user-committee
>Ämne: Re: [Openstack-operators] [publicClouds-wg] Public Cloud Working
>Group
>
>This sounds very interesting, put us down! :)
>
>On Tue, Nov 15, 2016 at 5:43 AM, matt Jarvis 
>wrote:
>> So after input from a variety of sources over the last few weeks, I'd
>> very much like to try and put together a public cloud working group,
>> with the very high level goal of representing the interests of the
>> public cloud provider community around the globe.
>>
>> I'd like to propose that, in line with the new process for creation of
>> working groups, we set up some initial IRC meetings for all interested
>> parties. The goals for these initial meetings would be :
>>
>> 1. Define the overall scope and mission statement for the working
>> group 2. Set out the constituency for the group - communication
>> methods, definitions of public clouds, meeting schedules, chairs etc.
>> 3. Identify areas of interest - eg. technical issues, collaboration
>> opportunities
>>
>> Before I go ahead and schedule first meetings, I'd very much like to
>> gather input from the community on interested parties, and if this
>> seems like a reasonable first step forward. My thought initially was
>> to schedule a first meeting on #openstack-operators and then decide on
>> best timings, locations and communication methods from there, but again
>>I'd welcome input.
>>
>> At this point it would seem to me that one of the key metrics for this
>> working group to be successful is participation as widely as possible
>> within the public cloud provider community, currently approximately 21
>> companies globally according to
>>https://www.openstack.org/marketplace/public-clouds/.
>> If we could get representation from all of those companies in any
>> potential working group, then that would clearly be the best outcome,
>> although that may be optimistic ! As has become clear at recent Ops
>> events, it may be that not all of those companies are represented on
>> these lists, so I'd welcome any input on the best way to reach out to
>>those folks.
>>
>> Matt
>>
>> ___
>> OpenStack-operators mailing list
>> OpenStack-operators@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operator
>> s
>>
>
>
>
>--
>Mohammed Naser ‹ vexxhost
>-
>D. 514-316-8872
>D. 800-910-1726 ext. 200
>E. mna...@vexxhost.com
>W. http://vexxhost.com
>
>___
>OpenStack-operators mailing list
>OpenStack-operators@lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>___
>OpenStack-operators mailing list
>OpenStack-operators@lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators