Open Stack

Hi Vasyl,

Thanks for your reply, will try and give feedback! :)

Regards,
Hieu

On Wed, Dec 20, 2017 at 9:49 PM, Vasyl Saienko <vsaienko at mirantis.com>
wrote:

> Hello,
>
> We using the following order when picking candidate port/portgroups when
> attaching VIFs:
>
>    - For Ironic <= Ocata
>    1. portgroups
>       2. ports with pxe_enabled=True
>       3. any other ports
>
>       - For Ironic >= Pike (port has new attribute physical_netowrk:
>       1. portgroups with physical_network field set
>       2. ports with physical_network field set
>       3. portgroups without physical_network field
>       4. ports without physical_network field
>       5. ports with pxe_enabled = True
>       6. other ports
>
> In both cases pxe_enabled ports are prefered when connecting tenant VIF
> compare to non-pxe ports.
> You can configure fake portgroup with 1 port if you using Ironic <= Ocata
> and Ironic will attach tenant VIF to portgroup (which will be actually your
> second port). The drawback here is that nova will do portgroup
> configuration via cloudinit on the instance.
> Or add physical_network field to port you want to connect tenant network
> to, but do not add it to other ports. Will work with ironic >= Pike
>
>
> https://github.com/openstack/ironic/blob/stable/pike/
> ironic/drivers/modules/network/common.py#L506
>
> On Wed, Dec 20, 2017 at 3:10 PM, Hieu LE <hieulq19 at gmail.com> wrote:
>
>> Hello Ironic guys,
>>
>> In my lab environment, I have finished setting up the multi-tenant
>> network environment for Ironic using networking-generic-switch (Cisco IOS
>> device). The official Ironic doc only talked about one BM node with one
>> port for provisioning and tenant network.
>>
>> My process here: I have created 2 ports, 01 port with pxe_enabled for
>> provisioning network and remaining port with pxe disabled; then using nova
>> boot with --nic option, hoping it can get network information via Neutron.
>> But it failed.
>>
>> So my question here is:
>> 1. Is this possible for enroll a node, then start provisioning it via one
>> port and then configuring tenant network via another port?
>> 2. Is my process correct, if not, could you provide some guides for the
>> right way?
>>
>> Thanks,
>> Hieu.
>>
>> --
>> -----BEGIN GEEK CODE BLOCK-----
>> Version: 3.1
>> GCS/CM/IT/M/MU d-@? s+(++):+(++) !a C++++(++++)$ ULC++++(++)$ P
>> L++(+++)$ E !W N* o+ K w O- M V- PS+ PE++ Y+ PGP+ t 5 X R tv+ b+(++)>+++
>> DI- D+ G e++(+++) h-- r(++)>+++ y-
>> ------END GEEK CODE BLOCK------
>>
>> ____________________________________________________________
>> ______________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/CM/IT/M/MU d-@? s+(++):+(++) !a C++++(++++)$ ULC++++(++)$ P L++(+++)$ E
!W N* o+ K w O- M V- PS+ PE++ Y+ PGP+ t 5 X R tv+ b+(++)>+++ DI- D+ G
e++(+++) h-- r(++)>+++ y-
------END GEEK CODE BLOCK------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171221/c11bcb39/attachment.html>