How to effectively deploy MAAS server inside the KVM with 2 interfaces and bridge them with physical host...












0















I have two servers on which I want to deploy MAAS and commission VM nodes. I don't have any physical small server with two interfaces (public and private), so I decided to deploy MAAS server inside the KVM.



I am unable to create two interfaces in MAAS KVM i.e., Private for the nodes and Public for the internet. Do i have to create two Virtual Networks in virt-manager for two interfaces of MAAS server KVM? How am I supposed to connect nodes(other VMs) with private network and expose them remotely?



I'm Stuck in this, it would be great if anyone could help me resolving these confusions?










share|improve this question





























    0















    I have two servers on which I want to deploy MAAS and commission VM nodes. I don't have any physical small server with two interfaces (public and private), so I decided to deploy MAAS server inside the KVM.



    I am unable to create two interfaces in MAAS KVM i.e., Private for the nodes and Public for the internet. Do i have to create two Virtual Networks in virt-manager for two interfaces of MAAS server KVM? How am I supposed to connect nodes(other VMs) with private network and expose them remotely?



    I'm Stuck in this, it would be great if anyone could help me resolving these confusions?










    share|improve this question



























      0












      0








      0








      I have two servers on which I want to deploy MAAS and commission VM nodes. I don't have any physical small server with two interfaces (public and private), so I decided to deploy MAAS server inside the KVM.



      I am unable to create two interfaces in MAAS KVM i.e., Private for the nodes and Public for the internet. Do i have to create two Virtual Networks in virt-manager for two interfaces of MAAS server KVM? How am I supposed to connect nodes(other VMs) with private network and expose them remotely?



      I'm Stuck in this, it would be great if anyone could help me resolving these confusions?










      share|improve this question
















      I have two servers on which I want to deploy MAAS and commission VM nodes. I don't have any physical small server with two interfaces (public and private), so I decided to deploy MAAS server inside the KVM.



      I am unable to create two interfaces in MAAS KVM i.e., Private for the nodes and Public for the internet. Do i have to create two Virtual Networks in virt-manager for two interfaces of MAAS server KVM? How am I supposed to connect nodes(other VMs) with private network and expose them remotely?



      I'm Stuck in this, it would be great if anyone could help me resolving these confusions?







      maas kvm






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 31 '18 at 18:47









      Sourav Ghosh

      39529




      39529










      asked Dec 22 '18 at 4:55









      Usama KhanUsama Khan

      11




      11






















          1 Answer
          1






          active

          oldest

          votes


















          0














          I just finished setting up a maas+juju cluster and while I'm waiting for some hardware, I did it all on a single machine inside KVM machines. It is a little involved and I'm probably going to write a blog at some point, but I'll try and get the gist of it here



          The main thing to realise is MAAS "needs" 2 interfaces in order to




          • connect to the internet

          • manage the cluster of machines it connects to by self managing various services, the most important being DHCP+tftp for pxe boot


          In the end, because I was having issues trying to bootstrap a juju controller inside a KVM machine with 2 nics, I ended up switching to a single interface for everything MAAS.



          I just had to make sure I met the requirement of providing a network interface that:




          • Had access to the internet

          • Did not have any external DHCP (pretty sure this isn't a hard requirement, but it made things far easier)


          To do that I created a KVM machine (but there's no reason you couldn't just use the host for this) to act as a gateway/router forwarding between 2 networks




          • My external internet-facing, dhcp-enabled subnet

          • A completely bare and unmanaged subnet (that MAAS now manages)


          A great couple of resources for this are




          • How to enabled ip forwarding and turn a unix box into a gateway


          • How to enabled port forwarding to expose a website (hint: the MAAS web ui)


          Once this is setup, you can create a KVM with a single NIC bridged to the NIC connected to the unmanaged subnet and install MAAS on it.



          Then connect all the machines you want MAAS to manage to the same unmanaged subnet and everything works perfectly.



          Bonus, you be able to setup the gateway box as a firewall to your MAAS cluster.



          I tried to cut back on many of the actually details, otherwise this would be an absolutely massive post. So feel free to ask clarifying questions if I left out too much detail.



          Failsafe -






          share|improve this answer








          New contributor




          failsafe is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.




















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1103734%2fhow-to-effectively-deploy-maas-server-inside-the-kvm-with-2-interfaces-and-bridg%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            I just finished setting up a maas+juju cluster and while I'm waiting for some hardware, I did it all on a single machine inside KVM machines. It is a little involved and I'm probably going to write a blog at some point, but I'll try and get the gist of it here



            The main thing to realise is MAAS "needs" 2 interfaces in order to




            • connect to the internet

            • manage the cluster of machines it connects to by self managing various services, the most important being DHCP+tftp for pxe boot


            In the end, because I was having issues trying to bootstrap a juju controller inside a KVM machine with 2 nics, I ended up switching to a single interface for everything MAAS.



            I just had to make sure I met the requirement of providing a network interface that:




            • Had access to the internet

            • Did not have any external DHCP (pretty sure this isn't a hard requirement, but it made things far easier)


            To do that I created a KVM machine (but there's no reason you couldn't just use the host for this) to act as a gateway/router forwarding between 2 networks




            • My external internet-facing, dhcp-enabled subnet

            • A completely bare and unmanaged subnet (that MAAS now manages)


            A great couple of resources for this are




            • How to enabled ip forwarding and turn a unix box into a gateway


            • How to enabled port forwarding to expose a website (hint: the MAAS web ui)


            Once this is setup, you can create a KVM with a single NIC bridged to the NIC connected to the unmanaged subnet and install MAAS on it.



            Then connect all the machines you want MAAS to manage to the same unmanaged subnet and everything works perfectly.



            Bonus, you be able to setup the gateway box as a firewall to your MAAS cluster.



            I tried to cut back on many of the actually details, otherwise this would be an absolutely massive post. So feel free to ask clarifying questions if I left out too much detail.



            Failsafe -






            share|improve this answer








            New contributor




            failsafe is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.

























              0














              I just finished setting up a maas+juju cluster and while I'm waiting for some hardware, I did it all on a single machine inside KVM machines. It is a little involved and I'm probably going to write a blog at some point, but I'll try and get the gist of it here



              The main thing to realise is MAAS "needs" 2 interfaces in order to




              • connect to the internet

              • manage the cluster of machines it connects to by self managing various services, the most important being DHCP+tftp for pxe boot


              In the end, because I was having issues trying to bootstrap a juju controller inside a KVM machine with 2 nics, I ended up switching to a single interface for everything MAAS.



              I just had to make sure I met the requirement of providing a network interface that:




              • Had access to the internet

              • Did not have any external DHCP (pretty sure this isn't a hard requirement, but it made things far easier)


              To do that I created a KVM machine (but there's no reason you couldn't just use the host for this) to act as a gateway/router forwarding between 2 networks




              • My external internet-facing, dhcp-enabled subnet

              • A completely bare and unmanaged subnet (that MAAS now manages)


              A great couple of resources for this are




              • How to enabled ip forwarding and turn a unix box into a gateway


              • How to enabled port forwarding to expose a website (hint: the MAAS web ui)


              Once this is setup, you can create a KVM with a single NIC bridged to the NIC connected to the unmanaged subnet and install MAAS on it.



              Then connect all the machines you want MAAS to manage to the same unmanaged subnet and everything works perfectly.



              Bonus, you be able to setup the gateway box as a firewall to your MAAS cluster.



              I tried to cut back on many of the actually details, otherwise this would be an absolutely massive post. So feel free to ask clarifying questions if I left out too much detail.



              Failsafe -






              share|improve this answer








              New contributor




              failsafe is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.























                0












                0








                0







                I just finished setting up a maas+juju cluster and while I'm waiting for some hardware, I did it all on a single machine inside KVM machines. It is a little involved and I'm probably going to write a blog at some point, but I'll try and get the gist of it here



                The main thing to realise is MAAS "needs" 2 interfaces in order to




                • connect to the internet

                • manage the cluster of machines it connects to by self managing various services, the most important being DHCP+tftp for pxe boot


                In the end, because I was having issues trying to bootstrap a juju controller inside a KVM machine with 2 nics, I ended up switching to a single interface for everything MAAS.



                I just had to make sure I met the requirement of providing a network interface that:




                • Had access to the internet

                • Did not have any external DHCP (pretty sure this isn't a hard requirement, but it made things far easier)


                To do that I created a KVM machine (but there's no reason you couldn't just use the host for this) to act as a gateway/router forwarding between 2 networks




                • My external internet-facing, dhcp-enabled subnet

                • A completely bare and unmanaged subnet (that MAAS now manages)


                A great couple of resources for this are




                • How to enabled ip forwarding and turn a unix box into a gateway


                • How to enabled port forwarding to expose a website (hint: the MAAS web ui)


                Once this is setup, you can create a KVM with a single NIC bridged to the NIC connected to the unmanaged subnet and install MAAS on it.



                Then connect all the machines you want MAAS to manage to the same unmanaged subnet and everything works perfectly.



                Bonus, you be able to setup the gateway box as a firewall to your MAAS cluster.



                I tried to cut back on many of the actually details, otherwise this would be an absolutely massive post. So feel free to ask clarifying questions if I left out too much detail.



                Failsafe -






                share|improve this answer








                New contributor




                failsafe is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.










                I just finished setting up a maas+juju cluster and while I'm waiting for some hardware, I did it all on a single machine inside KVM machines. It is a little involved and I'm probably going to write a blog at some point, but I'll try and get the gist of it here



                The main thing to realise is MAAS "needs" 2 interfaces in order to




                • connect to the internet

                • manage the cluster of machines it connects to by self managing various services, the most important being DHCP+tftp for pxe boot


                In the end, because I was having issues trying to bootstrap a juju controller inside a KVM machine with 2 nics, I ended up switching to a single interface for everything MAAS.



                I just had to make sure I met the requirement of providing a network interface that:




                • Had access to the internet

                • Did not have any external DHCP (pretty sure this isn't a hard requirement, but it made things far easier)


                To do that I created a KVM machine (but there's no reason you couldn't just use the host for this) to act as a gateway/router forwarding between 2 networks




                • My external internet-facing, dhcp-enabled subnet

                • A completely bare and unmanaged subnet (that MAAS now manages)


                A great couple of resources for this are




                • How to enabled ip forwarding and turn a unix box into a gateway


                • How to enabled port forwarding to expose a website (hint: the MAAS web ui)


                Once this is setup, you can create a KVM with a single NIC bridged to the NIC connected to the unmanaged subnet and install MAAS on it.



                Then connect all the machines you want MAAS to manage to the same unmanaged subnet and everything works perfectly.



                Bonus, you be able to setup the gateway box as a firewall to your MAAS cluster.



                I tried to cut back on many of the actually details, otherwise this would be an absolutely massive post. So feel free to ask clarifying questions if I left out too much detail.



                Failsafe -







                share|improve this answer








                New contributor




                failsafe is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                share|improve this answer



                share|improve this answer






                New contributor




                failsafe is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                answered Jan 9 at 5:41









                failsafefailsafe

                13




                13




                New contributor




                failsafe is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.





                New contributor





                failsafe is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






                failsafe is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1103734%2fhow-to-effectively-deploy-maas-server-inside-the-kvm-with-2-interfaces-and-bridg%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

                    is 'sed' thread safe

                    How to make a Squid Proxy server?