Thanks. After some digging around, I figured it out and it’s basically exactly what you said. I found what I was looking for under the Traffic Types in the Physical Network config. This is where the ranges are defined for Management/Guest/Public/Storage. I had some really strange ranges defined here mostly due to not knowing what I was doing when I set this up some time ago. It makes a lot more sense now. I limited the ranges available to the system vms and now I can predict the IP being used by the system vms. So I guess it’s not so much the second interface as it was that I had no idea where the private IP was being pulled from. It’s obvious now it’s from the Management range in the Physical Network config.
-jeremy > On Monday, Feb 28, 2022 at 3:51 AM, vas...@gmx.de <vas...@gmx.de > (mailto:vas...@gmx.de)> wrote: > Hi Jeremy, > > Public : Accessible / reachable from outside of the CS environment; are not > controlled and managed by CS. Has nothing to do with the usal terminology > regarding "IP-Adresses". > Private: Internal networks within the cloudstack environment - management / > storage / guesttraffic (if not using "L2 Network" ServiceOfferings). > > I guess you are trying to set up something like what is called > "small-scale" deployment. > which time of zones did you deploy / use for testing? > > The IP adress for system VMs is configured at the zonecreation. you are > providing there a IP address range for systemVMs. This is stored in the CS > - Database. If the machine reboots the system VM will get the ip out the > pool of "assigned" ip adresses. > You should find theses in the networksettings of the zone you have > deployend. There you can configure the range of availeable ips for > systemvms. > > Regards > Chris > > Am Mo., 28. Feb. 2022 um 10:59 Uhr schrieb Jeremy Hansen > <jer...@skidrow.la.invalid>: > > > I’m not talking about public as in externally routable IPs. The system vms > > use the terminology of public and private IPs which in my case is just two > > IPs on the same internal subnet so it seems redundant for no real reason. > > In my case public and private is the same network so why have two > > interfaces that are on the same network on each system vm? > > > > I want to control the IPs that get assigned to the system vm’s so I can > > avoid IPs conflicts. I’d like the system vm’s to allocate from the same > > dhcp server the guests vm are pulling from over the L2 network. If it gets > > its ip from dhcp like everything else, I won’t have to worry about IP > > conflicts when the system vm’s seem to just randomly assign IPs that could > > be the ip of another device on the network. I basically just want > > everything to use the dhcp server I’m running external to Cloudstack. > > > > Thanks > > > > > > > > > > > > On Monday, Feb 28, 2022 at 1:31 AM, Nux! <n...@li.nux.ro> wrote: > > > > > > What do you mean by "static IPs"? > > > > The system vms will continue to need the usual networks in Cloudstack. > > > > You will need to look at the "management" and "public" (and "secondary > > storage" if you specified that expressly) networks in Cloudstack, see if > > there are any changes you can do to integrate it in your environment. > > > > Don't forget, none of said networks actually need to use "public" IPs, > > you can operate entirely in the realm of RFC 1918, this may help you > > juggle things around. > > > > --- > > Nux! > > www.nux.ro [1] > > > > On 2022-02-28 07:25, Jeremy Hansen wrote: > > > > One more question related to this. I see System VMs are still using > > static IPs. I'm not sure where they're pulled from since I've removed > > the shared network completely and I'm only using L2 now. > > > > Also, the System VMs have a Public and Private IP, but in my case, > > everything is on a flat network and these interfaces are just getting > > two IPs for the same network. Can I disable one of these interfaces to > > simplify things without breaking things? > > > > Thanks > > -jeremy > > > > On Saturday, Feb 26, 2022 at 3:20 AM, Jeremy Hansen <jer...@skidrow.la> > > wrote: > > > > Figured it out. Thanks again. The L2 network is exactly what I > > needed. > > > > -jeremy > > > > On Saturday, Feb 26, 2022 at 2:38 AM, Jeremy Hansen <jer...@skidrow.la> > > wrote: > > > > Thank you. I'm working out the L2 config now but it appears to be > > working. My next question, is it possible to transition existing VMs > > to a new guest network? I didn't see anything obvious. Cloudmonkey? > > > > -jeremy > > > > On Saturday, Feb 26, 2022 at 1:07 AM, Wei ZHOU <ustcweiz...@gmail.com> > > wrote: > > HI Jeremy, > > > > You can use L2 network. > > > > It is not system VMS stealing ip, but might because you set wrong ip > > range > > when you added the pod. > > > > Wei > > > > On Saturday, 26 February 2022, Jeremy Hansen > > <jer...@skidrow.la.invalid> > > wrote: > > > > Is there a way to run Cloudstack without a virtual router? I basically > > want CS to handle the management of vm's but I'd like to use outside > > network services for dhcp/ip allocation. Separate dhcp server not > > managed > > by CS? Is this possible? > > > > How can I dictate the IPs used by infrastructure VMs? I'm running in to > > IP conflicts because system vm's keep stealing IPs that are already > > being > > used. > > > > Thanks > > > > > > > > Links: > > ------ > > [1] http://www.nux.ro > > > >
signature.asc
Description: PGP signature
