Exact, that will work find. But keep in mind an offering without storage tag will be deployed on any primary storage that have space.
Le 8 mai 2017 3:40 PM, "Sebastian Gomez" <[email protected]> a écrit : > If I have understood correctly: > > Tag each primary storage (p.e. SSD and NLSAS), then create a different > service offering for each storage tag (when you create a Service offering - > cpu, mem, etc.- you can set the related storage tag, use SSD for one and > NLSAS for the other). > When you create the MV, the service offering will determine the storage > tier using the storage tag. > > Regards. > > > > > Atentamente, > Sebastián Gómez > > On Mon, May 8, 2017 at 8:50 AM, Ivan Kudryavtsev <[email protected] > > > wrote: > > > Hi, Imran. Use service offering tags and corresponding storage tags. If > you > > want to have one service offering and two different storages when > > installing from templates, then I don't know otheroptions than use > > different zones. Maybe someone knows other approach. > > > > 8 мая 2017 г. 13:27 пользователь "Imran Ahmed" <[email protected]> > написал: > > > > Dear Team, > > > > I have two primary storages in my CloudStack 4.9 (KVM based) . One of > the > > primary storages is composed of SSD disks and the other is SATA. > > Can I select the primary storage to use while spinning a new guest VM. > > Like > > for example If I want to spin up a VM using SSD based primary storage . > > Please suggest how can I achieve this. > > > > Kind regards, > > > > Imran > > >
