Hi Ugo, I dont know if you have multiple SSVM (and other system) offerings, but we have 2 default ones for every role (SSVM on local and on shared storage, then CPVM on local and shared, then VR for both also...) - and we just edit the "shared one" i.e. System Offering For Secondary Storage VM and set tag here, which was previously also set on new storage.
They way tagging works for volumes (descriptive) as following, assuming you have setup "TAG1" as the tag on the storage side: - list all storages that have tag "TAG1" on them.... and then ACS will list all storages (if you have multiple storages) that have this flag, and usually the first one (or randomly, not sure) is choosen for volume deployment... This doesn't stop UNTAGGED offerings, to also "deploy" volumes on this TAGGED storages, since then ACS list all storages (with no TAG filters/limit) and then choose from the list... If you do this for VRs also, make sure to restart VPC (new VR with new name crated, taking into account Offering), while simple VR reboot (translates to destroy and create) will result on VR recreated with same name on same storage where it was originally (my experience). Not sure if this helps. On 6 February 2018 at 16:26, Ugo Vasi <ugo.v...@procne.it> wrote: > Hi Andrija, > do I have to eliminate other system offers that do not have storage tag > before destroy the SVM? > > > Il 02/02/2018 17:32, Andrija Panic ha scritto: > >> If you can afford using (Storage) Tags, then you can do it that way also. >> >> we have 3 different storages (had) and all 3 were having at some time >> different TAGs - you edit existing System Offering for the CPVM, SSVM, VR >> (and/or Compute and Data disk offerings) i.e. //Service Offerings -> >> System Offerings -> System Offering For Secondary Storage VM... and define >> storage tag. >> just make sure you put same tag on offering as you put on new storage, and >> than go and destroy systemVMs - and they will be automatically recreated >> after 1-2 minutes, but since tagging is present they will be created on >> the >> proper storage. >> >> >> >> >> >> >> On 24 January 2018 at 16:35, Dag Sonstebo <dag.sonst...@shapeblue.com> >> wrote: >> >> Hi Ugo, >>> >>> If all you are worried about is the system VMs then the easiest and risk >>> free option is: >>> >>> - Configured new primary storage pool. >>> - Disable the old one (you will have to do this with cloudmonkey, it is >>> not available through the GUI – something like update storagepool >>> enabled=false id=50848ff7-c6aa-3fdd-b487-27899bf2129c) >>> - Destroy your system VMs and watch them come back online on new primary >>> storage. >>> - If for some reason it doesn't work then just re-enable the old storage >>> and do some troubleshooting. >>> >>> Regards, >>> Dag Sonstebo >>> Cloud Architect >>> ShapeBlue >>> >>> From: Özhan Rüzgar Karaman <oruzgarkara...@gmail.com> >>> Date: Wednesday, 24 January 2018 at 14:25 >>> To: Ugo Vasi <ugo.v...@procne.it> >>> Cc: "users@cloudstack.apache.org" <users@cloudstack.apache.org>, Dag >>> Sonstebo <dag.sonst...@shapeblue.com> >>> Subject: Re: Migrate system VMs volumes to new storage >>> >>> Hi Ugo; >>> If you have running other vm's over it then you could not remove primary >>> storage. If you want to remove primary storage then you need to migrate >>> vm's to other storage first then make it empty and you could disable & >>> remove. >>> >>> So maybe updating system offerings could help you to change reprovisioned >>> SSVM's disk location. >>> >>> Thanks >>> Özhan >>> >>> 2018-01-24 17:15 GMT+03:00 Ugo Vasi <ugo.v...@procne.it<mailto:ugo >>> .v...@procne.it>>: >>> Hi Özhan, >>> can I disable the zone and remove primary storage with running VM on it? >>> >>> >>> >>> >>> On 24/01/2018 14:56, Özhan Rüzgar Karaman wrote: >>> Hi Ugo; >>> When you destroy systemvm's, disable zone, disable and remove primary >>> storage and add new primary storage and enable zone, new system vms will >>> automatically provision on new primary storage. >>> >>> Thanks >>> Özhan >>> >>> 2018-01-24 16:50 GMT+03:00 Ugo Vasi <ugo.v...@procne.it<mailto:ugo >>> .v...@procne.it>>: >>> Hi Dag, >>> I have to dismiss a primary storage, not the secondary. Do I have to >>> create or modify a system offering with a storage tag and destroy the >>> system-vm? In this case, how can I be sure that the SVM will be recreated >>> using just that system offering? >>> >>> >>> >>> On 24/01/2018 14:40, Dag Sonstebo wrote: >>> Hi Ugo, >>> >>> If this is just system VMs you can just make sure the system VM template >>> has been copied and is present on your new secondary storage, then >>> disable >>> the old secondary storage and destroy the system VMs – they should start >>> again (they are stateless so you don’t need to worry about copying image >>> files etc.) >>> >>> Regards, >>> Dag Sonstebo >>> Cloud Architect >>> ShapeBlue >>> >>> On 24/01/2018, 09:56, "Ugo Vasi" <ugo.v...@procne.it<mailto:ugo >>> .v...@procne.it>> wrote: >>> >>> Hi all, >>> I have to dismiss a storage nas where the system VMs image files >>> are >>> resident (kvm hypervisor on nfs storage). >>> From the web interface I can not do it like normal VMs. >>> The system vms are all cloned starting from the same image and >>> have >>> backing files in the same (old) storage, then copying the file I >>> have >>> the reference to the storage that I have to >>> <https://maps.google.com/?q=reference+to+the+storage+that+I+have+to&entry=gmail&source=g> >>> remove. >>> How can I proceed? >>> -- >>> *Ugo Vasi* / System Administrator >>> ugo.v...@procne.it<mailto:ugo.v...@procne.it> <mailto: >>> ugo.v...@procne.it<mailto:ugo.v...@procne.it>> >>> *Procne S.r.l.* >>> +39 0432 486 523<tel:%2B39%200432%20486%20523> >>> via Cotonificio, 45 >>> 33010 Tavagnacco (UD) >>> www.procne.it<http://www.procne.it> <http://www.procne.it/> >>> Le informazioni contenute nella presente comunicazione >>> ed >>> i relativi >>> allegati possono essere riservate e sono, comunque, destinate >>> esclusivamente alle persone od alla Società sopraindicati. La >>> diffusione, distribuzione e/o copiatura del documento trasmesso da >>> parte >>> di qualsiasi soggetto diverso dal destinatario è proibita sia ai >>> sensi >>> dell'art. 616 c.p., che ai sensi del Decreto Legislativo n. >>> 196/2003 >>> "Codice in materia di protezione dei dati personali". Se avete >>> ricevuto >>> questo messaggio per errore, vi preghiamo di di >>> <https://maps.google.com/?q=esto+messaggio+per+errore,+vi+ >>> preghiamo+di+di&entry=gmail&source=g>struggerlo >>> >>> e di informare >>> immediatamente Procne S.r.l. scrivendo all' ind< >>> https://maps.google.com/?q=atamente+Procne+S.r.l.+ >>> scrivendo+all'+ind&entry=gmail&source=g>irizzo e-mail >>> i...@procne.it<mailto:i...@procne.it> <mailto:i...@procne.it >>> <mailto: >>> i...@procne.it>>. >>> >>> >>> dag.sonst...@shapeblue.com<mailto:dag.sonst...@shapeblue.com> >>> www.shapeblue.com<http://www.shapeblue.com> >>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK >>> @shapeblue >>> >>> >>> >>> >>> -- >>> >>> *Ugo Vasi* / System Administrator >>> ugo.v...@procne.it<mailto:ugo.v...@procne.it> <mailto:ugo.v...@procne.it >>> < >>> mailto:ugo.v...@procne.it>> >>> >>> >>> >>> >>> *Procne S.r.l.* >>> +39 0432 486 523<tel:%2B39%200432%20486%20523> >>> via Cotonificio, 45 >>> 33010 Tavagnacco (UD) >>> www.procne.it<http://www.procne.it> <http://www.procne.it/> >>> >>> >>> Le informazioni contenute nella presente comunicazione ed i relativi >>> allegati possono essere riservate e sono, comunque, destinate >>> esclusivamente alle persone od alla Società sopraindicati. La diffusione, >>> distribuzione e/o copiatura del documento trasmesso da parte di qualsiasi >>> soggetto diverso dal destinatario è proibita sia ai sensi dell'art. 616 >>> c.p., che ai sensi del Decreto Legislativo n. 19< >>> https://maps.google.com/?q=he+ai+sensi+del+Decreto+ >>> Legislativo+n.+19&entry=gmail&source=g>6/2003 "Codice in materia >>> di protezione dei dati personali". Se avete ricevuto questo messaggio per >>> errore, vi preghiamo di distruggerlo e di informare immediatamente Procne >>> S.r.l. scrivendo all' indirizzo e-mail i...@procne.it<mailto:info@ >>> procne.it> <mailto: >>> i...@procne.it<mailto:i...@procne.it>>. >>> >>> >>> >>> >>> >>> -- >>> >>> *Ugo Vasi* / System Administrator >>> ugo.v...@procne.it<mailto:ugo.v...@procne.it> <mailto:ugo.v...@procne.it >>> < >>> mailto:ugo.v...@procne.it>> >>> >>> >>> >>> >>> *Procne S.r.l.* >>> +39 0432 486 523<tel:%2B39%200432%20486%20523> >>> via Cotonificio, 45 >>> 33010 Tavagnacco (UD) >>> www.procne.it<http://www.procne.it> <http://www.procne.it/> >>> >>> >>> Le informazioni contenute nella presente comunicazione ed i relativi >>> allegati possono essere riservate e sono, comunque, destinate >>> esclusivamente alle persone od alla Società sopraindicati. La diffusione, >>> distribuzione e/o copiatura del documento trasmesso da parte di qualsiasi >>> soggetto diverso dal destinatario è proibita sia ai sensi dell'art. 616 >>> c.p., che ai sensi del Decreto Legislativo n. 196/2003 "Codice in materia >>> di protezione dei dati personali". Se avete ricevuto questo messaggio per >>> errore, vi preghiamo di distruggerlo e di informare immediatamente Procne >>> S.r.l. scrivendo all' indirizzo e-mail i...@procne.it<mailto:info@ >>> procne.it> <mailto:i...@procne.it<mailto:i...@procne.it>>. >>> >>> >>> dag.sonst...@shapeblue.com >>> www.shapeblue.com >>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK >>> @shapeblue >>> >>> >>> >>> >>> >> > > -- > > *Ugo Vasi* / System Administrator > ugo.v...@procne.it <mailto:ugo.v...@procne.it> > > > > > *Procne S.r.l.* > +39 0432 486 523 > via Cotonificio, 45 > 33010 Tavagnacco (UD) > www.procne.it <http://www.procne.it/> > > > Le informazioni contenute nella presente comunicazione ed i relativi > allegati possono essere riservate e sono, comunque, destinate > esclusivamente alle persone od alla Società sopraindicati. La diffusione, > distribuzione e/o copiatura del documento trasmesso da parte di qualsiasi > soggetto diverso dal destinatario è proibita sia ai sensi dell'art. 616 > c.p., che ai sensi del Decreto Legislativo n. 196/2003 "Codice in materia > di protezione dei dati personali". Se avete ricevuto questo messaggio per > errore, vi preghiamo di distruggerlo e di informare immediatamente Procne > S.r.l. scrivendo all' indirizzo e-mail i...@procne.it <mailto: > i...@procne.it>. > > > > > -- Andrija Panić
