I'm running Mirantis OS 9.2 and using VLANs so you should be able to as well without using OS11. It should provide you the option to use VLAN segmentation for networking while running the cloud environment creation wizard. Once you create the cloud environment, you can't change this option, you must re-create the cloud to do so(as far as I'm aware of).

On 04/13/2017 12:19 PM, Konstantin Raskoshnyi wrote:
Yes, you must be right.
I'm using the old Mirantis OS 9.2, there's no suck options like
Vlan. Only flat network.
I'll take a look on OS11

Thanks

On Thu, Apr 13, 2017 at 9:24 AM, sil...@gmail.com
<mailto:sil...@gmail.com> <sil...@gmail.com <mailto:sil...@gmail.com>>
wrote:

    This is only if you're using the controllers to serve as a gateway
    to the Internet or to direct incoming traffic to the VMs.

    If you use a VLAN only network configuration to offload the gateway
    to an external device (router or l3 switch) or you use Neutron in
    DVR mode, this shouldn't be an issue.

    On 04/13/2017 10:49 AM, Konstantin Raskoshnyi wrote:

        If all controllers are down - nova is down and vms won't be able to
        access network

        On Thu, Apr 13, 2017 at 5:33 AM Adam Lawson <alaw...@aqorn.com
        <mailto:alaw...@aqorn.com>
        <mailto:alaw...@aqorn.com <mailto:alaw...@aqorn.com>>> wrote:

            Another FYI, OpenStack services don't have to be running to
        access a
            virtual machine. Period. Amy other condition that prevents
        this is a
            serious design flaw.

            //adam

            On Apr 13, 2017 5:31 AM, wrote:

                Fyi, the idea of controllers are a bit of a misnomer.
        You should
                have redundant services; they don't necessarily need to
        be on
                the same box. Since your asking as a new user. Have fun!

                //adam

                On Apr 12, 2017 5:27 PM, "Konstantin Raskoshnyi"
                <konra...@gmail.com <mailto:konra...@gmail.com>
        <mailto:konra...@gmail.com <mailto:konra...@gmail.com>>> wrote:

                    Yes, machines are still running, but since neutron
        is down
                    none of them can be accessible.

                    On Wed, Apr 12, 2017 at 5:10 PM ron ramos
        <nha...@gmail.com <mailto:nha...@gmail.com>
                    <mailto:nha...@gmail.com <mailto:nha...@gmail.com>>>
        wrote:

                        hi,

                        depends on what you mean by inaccessible, your VM is
                        probably still up and running on the compute
        node. but
                        you won't be able to access them remotely as your
                        controller node ( which is hosting neutron ) is
        down.

                        regards,
                        nhadie


                        On Apr 12, 2017 11:31, "Konstantin Raskoshnyi"
                        <konra...@gmail.com <mailto:konra...@gmail.com>
        <mailto:konra...@gmail.com <mailto:konra...@gmail.com>>> wrote:

                            Hi guys,
                            I'm new to openstack.
                            Installed mirantis os 9,
                            If one of controllers goes down - vm
        machines are
                            not accesible, I though openstack supposed
        to work
                            even if one controller is alive

                            Any thoughts?

                            _______________________________________________
                            Mailing list:

        http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
        <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>
                            Post to     : openstack@lists.openstack.org
        <mailto:openstack@lists.openstack.org>
                            <mailto:openstack@lists.openstack.org
        <mailto:openstack@lists.openstack.org>>
                            Unsubscribe :

        http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
        <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>


                    _______________________________________________
                    Mailing list:

        http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
        <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>
                    Post to     : openstack@lists.openstack.org
        <mailto:openstack@lists.openstack.org>
                    <mailto:openstack@lists.openstack.org
        <mailto:openstack@lists.openstack.org>>
                    Unsubscribe :

        http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
        <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>



        _______________________________________________
        Mailing list:
        http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
        <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>
        Post to     : openstack@lists.openstack.org
        <mailto:openstack@lists.openstack.org>
        Unsubscribe :
        http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
        <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>



    _______________________________________________
    Mailing list:
    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
    <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>
    Post to     : openstack@lists.openstack.org
    <mailto:openstack@lists.openstack.org>
    Unsubscribe :
    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
    <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>




_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Reply via email to