I discovered how to enable the ConfigDrive network service provider. But I get this message when I try to create a network with the DefaultL2NetworkOfferingConfigDrive network offering: Error: (HTTP 431, error code 4350) Only AclType=Domain can be specified for network creation in Basic zone If I add aclType=Domain, I get this message: Error: (HTTP 431, error code 4350) Only Shared networks can have aclType=Domain -Stu ________________________________ From: Stuart Whitman <swhit...@groupw.com> Sent: Wednesday, January 25, 2023 5:28 PM To: users@cloudstack.apache.org <users@cloudstack.apache.org> Subject: Re: Creating a guest network
Thanks for the help Daan! The zone is enabled. Using cloudmonkey, I tried: create network networkofferingid=920fe353-4776-4430-a703-d7eafd2bdb92 name=DefaultGuest displaytext=Guest zoneid=d4e6cd44-163f-4179-b670-9af24c62ffab Which produced the error: Error: (HTTP 530, error code 4390) Provider ConfigDrive is either not enabled or doesn't support service UserData in physical network id=204 Not knowing what that error meant, I tried to create the network I deleted: create network networkofferingid=d45e3f7e-231d-4ebe-8f95-2f412aa6f7b1 name=DefaultGuest displaytext=Guest zoneid=d4e6cd44-163f-4179-b670-9af24c62ffab And got: Error: (HTTP 431, error code 4350) Only AclType=Domain can be specified for network creation in Basic zone So I tried: create network networkofferingid=d45e3f7e-231d-4ebe-8f95-2f412aa6f7b1 name=DefaultGuest displaytext=Guest zoneid=d4e6cd44-163f-4179-b670-9af24c62ffab acltype=Domain Which returned: Error: (HTTP 431, error code 4350) Only Shared networks can have aclType=Domain I'm not sure what else to try. ________________________________ From: Daan Hoogland <daan.hoogl...@gmail.com> Sent: Wednesday, January 25, 2023 10:39 AM To: swhit...@groupw.com.invalid <swhit...@groupw.com.invalid> Cc: users@cloudstack.apache.org <users@cloudstack.apache.org> Subject: Re: Creating a guest network @stu, I think you either hit a bug or haven't enabled your zone. You can try using cloudmonkey to add the offering. I have not much experience with basic zones, but I think this should work. On Wed, Jan 25, 2023 at 3:11 PM Stuart Whitman <swhit...@groupw.com.invalid> wrote: > Hello, > > I was able to get a CloudStack cluster up and running. Using these > instructions, > https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fleo.leung.xyz%2Fwiki%2FCloudStack&data=05%7C01%7Cswhitman%40groupw.com%7Cb6d3b11f52f5430257cb08dafeea9dc1%7C5746ff41c91e439b81427cff90226280%7C0%7C0%7C638102582947261424%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=lQGBWn1b5pyjhg%2Fm7ohannMD5IsIfYVae6SxHjCuhq4%3D&reserved=0, > I was able to create > a simple Rocky Linux 8 instance, but I failed to create an instance using > user data to create an account. I read that the network must offer the > "User Data" service offering. I tried to make another guest network but > failed because the Zone pull-down list was empty. I selected basic > networking when I created the zone. I deleted the guest network, thinking > that basic networking could only have one guest network. However, when I > try to re-create a guest network, the zone pull-down list is still empty. > > How do I create guest networks? > > Thanks > -Stu > _____________________________________ > The information contained in this e-mail and any attachments from Group W > may contain confidential and/or proprietary information and is intended > only for the named recipient to whom it was originally addressed. If you > are not the intended recipient, be aware that any disclosure, distribution, > or copying of this e-mail or its attachments is strictly prohibited. If you > have received this e-mail in error, please notify the sender immediately of > that fact by return e-mail and permanently delete the e-mail and any > attachments to it. > -- Daan _____________________________________ The information contained in this e-mail and any attachments from Group W may contain confidential and/or proprietary information and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, be aware that any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately of that fact by return e-mail and permanently delete the e-mail and any attachments to it.
