On 6/6/12 11:46 AM, "de Jong, Mark-Jan" <[email protected]> wrote:
> > >> -----Original Message----- >> From: Alena Prokharchyk [mailto:[email protected]] >> Sent: Wednesday, June 06, 2012 2:35 PM >> To: [email protected] >> Subject: Re: Change network offering on Shared network >> >> On 6/6/12 11:20 AM, "de Jong, Mark-Jan" <[email protected]> >> wrote: >> >> > >> > >> >> -----Original Message----- >> >> From: Alena Prokharchyk [mailto:[email protected]] >> >> Sent: Wednesday, June 06, 2012 2:11 PM >> >> To: [email protected] >> >> Subject: Re: Change network offering on Shared network >> >> >> >> On 6/6/12 11:05 AM, "de Jong, Mark-Jan" <[email protected]> >> >> wrote: >> >> >> >> >> -----Original Message----- >> >> >> From: Alena Prokharchyk [mailto:[email protected]] >> >> >> Sent: Wednesday, June 06, 2012 1:59 PM >> >> >> To: [email protected] >> >> >> Subject: Re: Change network offering on Shared network >> >> >> >> >> >> On 6/6/12 10:50 AM, "de Jong, Mark-Jan" >> >> >> <[email protected]> >> >> >> wrote: >> >> >> >> >> >> >Hello, >> >> >> >I want to change the network offering on a shared network in an >> >> >> >attempt to disable the virtual router but am getting an error. I >> >> >> >have run the following API command: >> >> >> > >> >> >> >curl >> >> >> >http://localhost:8096/?command=updateNetwork&id=efd2ff02-bc35- >> 486 >> >> >> >7- >> >> >> 8367 >> >> >> >-84 >> >> >> >3ddebc0c96&networkofferingid=4fd6f8b4-4c67-4132-85f9- >> de1b428f53cc >> >> >> > >> >> >> >which results in the following error message in management- >> >> server.log. >> >> >> > >> >> >> >2012-06-06 13:07:12,466 DEBUG [cloud.async.AsyncJobManagerImpl] >> >> >> >(Job-Executor-3:job-256) Executing >> >> >> >com.cloud.api.commands.UpdateNetworkCmd for job-256 >> >> >> >2012-06-06 13:07:12,491 INFO [cloud.api.ApiDispatcher] >> >> >> >(Job-Executor-3:job-256) NetworkOffering and domain suffix >> >> >> >upgrade can be perfomed for Isolated networks only >> >> >> > >> >> >> >Is there a workaround? Can I alter the database directly to >> >> >> >disable >> >> >> the >> >> >> >networks virtual router? I was thinking of updating the networks >> >> >> >network offering in table "networks" and then deleting >> >> >> ntwk_service_map >> >> >> >entries for that particular network. >> >> >> >> >> >> >> >> >> Network offering upgrade is not supported for Shared networks. >> >> >> Changing the database won't do the job; initial Virtual router >> >> >> startup in network depends on the initial network offering - we >> >> >> set the network rate, dnsmasq settings, etc. So removing >> >> >> service_map is not going to change the network setup on the >> >> >> backend. Besides, if >> >> you >> >> >> remove entries from ntwk_service_map for the network, you have to >> >> >> re-insert it back based on the new network offering. >> >> >> >> >> >> What exactly you want to change for your network? >> >> >> >> >> >> -Alena. >> >> > >> >> >I want to disable the virtual router for that network as in the >> >> >following >> >> >article: >> >> > >> >> >http://remibergsma.wordpress.com/2012/03/10/howto-create-a-network- >> i >> >> >n- >> >> c >> >> >lou >> >> >dstack-without-a-virtual-router/ >> >> > >> >> >Thanks! >> >> >> >> >> >> >> >> External devices (Juniper SRX, F5, Netscaler) in Advance zone are >> >> supported for Isolated networks only. In Basic zone we support >> >> Netscaler for Shared network when elasticIP/elasticLB mode is on. >> >> >> >> For Shared networks in Advance zone only VirtualRouter is supported >> >> as a provider, so you can't change it. >> >> >> >> >> >> -Alena. >> > >> >I understand. But the article refers to a Virtual router with no >> >support services enabled so the virtual router never starts. That is >> >exactly what I want, given that I don't need the services provided by >> >the virtual router in the first place. >> >> >> >> >> I would always recommend to start clean: >> >> * create network offering with no services >> * create the network >> >> >> If you want to change the existing Shared network, here are the steps - >> note it that it was never tested as none-supported case, so you might >> end up with the failures: >> >> * Make sure you cleaned up all the rules for the network related to the >> original network offering services (userData if userData service was >> enabled, firewall rules if firewallRule service is enabled, etc) >> * destroy virtual router for your existing network. >> * create network offering with no services >> * update network in cloud.netwrorks with the new network_offering_id >> * remove all entries for the network in network_offering_service_map >> >> To test if the network is functional, start a new user vm in the >> network. >> >> -Alena. > >Awsome. That's exactly what I'm looking for.. For point #1 where can I >find the rules to clean up? As per ntwk_service_map, Userdata, Dhcp, and >Dns services are provided. > > >Thanks! Just one thing to check then - make sure user_data is null in user_vm table for the instances from your network, and you should be good to go. --Alena. > >> >> >> >> >> > >> >> >> >> >> >> >> >> > >> >> >> >update networks set network_offering_id=<new offering id> where >> >> >> id=209; >> >> >> >delete from ntwk_service_map where network_id=209; >> >> >> > >> >> >> >Thoughts? >> >> >> > >> >> >> >Thanks! >> >> >> > >> >> >> >Mark >> >> >> > >> >> >> > >> >> >> >________________________________ >> >> >> >PRIVILEGED AND CONFIDENTIAL >> >> >> >PLEASE NOTE: The information contained in this message is >> >> privileged >> >> >> >and confidential, and is intended only for the use of the >> >> individual >> >> >> to >> >> >> >whom it is addressed and others who have been specifically >> >> >> >authorized to receive it. If you are not the intended recipient, >> >> you >> >> >> >are hereby notified that any dissemination, distribution or >> >> >> >copying of this communication is strictly prohibited. If you >> have >> >> >> >received this communication in error, or if any problems occur >> >> >> >with transmission, please contact sender. Thank you. >> >> >> > >> >> >> >Please consider the environment before printing this e-mail. >> >> >> > >> >> >> >> >> > >> >> > >> >> >PRIVILEGED AND CONFIDENTIAL >> >> >PLEASE NOTE: The information contained in this message is >> privileged >> >> >and confidential, and is intended only for the use of the >> individual >> >> to >> >> >whom it is addressed and others who have been specifically >> >> >authorized to receive it. If you are not the intended recipient, >> you >> >> >are hereby notified that any dissemination, distribution or copying >> >> >of this communication is strictly prohibited. If you have received >> >> >this communication in error, or if any problems occur with >> >> >transmission, please contact sender. Thank you. >> >> > >> >> >Please consider the environment before printing this e-mail. >> >> > >> >> > >> >> >> > >> > >> >PRIVILEGED AND CONFIDENTIAL >> >PLEASE NOTE: The information contained in this message is privileged >> >and confidential, and is intended only for the use of the individual >> to >> >whom it is addressed and others who have been specifically authorized >> >to receive it. If you are not the intended recipient, you are hereby >> >notified that any dissemination, distribution or copying of this >> >communication is strictly prohibited. If you have received this >> >communication in error, or if any problems occur with transmission, >> >please contact sender. Thank you. >> > >> >Please consider the environment before printing this e-mail. >> > >> > >> > > >PRIVILEGED AND CONFIDENTIAL >PLEASE NOTE: The information contained in this message is privileged and >confidential, and is intended only for the use of the individual to whom >it is addressed and others who have been specifically authorized to >receive it. If you are not the intended recipient, you are hereby >notified that any dissemination, distribution or copying of this >communication is strictly prohibited. If you have received this >communication in error, or if any problems occur with transmission, >please contact sender. Thank you. > >Please consider the environment before printing this e-mail. > >
