Hi, now I got another problem.
I have two models of GPU devices and I set both in pci_alias and
pcli_passthrogh_whitelist on controller and compute node(with this two
GPUs).
Now I removed one of GPU and delete its data in nova.conf, then restart
nova-api, nova-scheduler (Controller) and nova-compu
Thanks Kevin,
This is another good option to solve IP problem for me. I'll note this.
Eddie.
2017-07-06 11:10 GMT+08:00 Kevin Benton :
> As a stop gap for the IP problem, keep in mind that you can create a
> neutron port separately and boot the instance to it. Then when you delete
> the instanc
Just a friendly reminder for those who are waking up on the other side of
the globe. Please take a moment to put some ideas for sessions in the
etherpad - https://etherpad.openstack.org/p/MEX-ops-meetup
Even if you are not able to make the midcycle, please take time to propose
sessions.
On Mon, J
As a stop gap for the IP problem, keep in mind that you can create a
neutron port separately and boot the instance to it. Then when you delete
the instance the port will remain and hold onto the IP so you can boot to
it with a different instance later.
On Jul 5, 2017 18:31, "Eddie Yen" wrote:
>
>> The instance can also be migrated between 2 Westmere hosts.
>> As I outline in another email, I suspect (perhaps incorrectly) as the
>> VM has "cpu mode='host-model'" in its running config, libvirt may be
>> comparing source and destination host CPUs and not guest and destination
>> CPUs.
>
>
Hi, thanks for reply first!
After I tried shelve instance, yes it really release GPU resources.
But as Dinesh said, can't unshelve this instance if all GPUs occupied.
Before known about shelve instance, I have do few approach.
One is using "resize" the instance's flavor to non-GPU flavor, but ca
Hi, regarding nova, I am not clear about fiber channel over ethernet
functionality, if it is necessary to configure something more for fiber
channel over ethernet on the compute side (we already configured fcoe
utils, lldpd, etc),
Doubt:
In the compute node have to be installed cinder-volume a
On 07/05/2017 04:18 AM, Eddie Yen wrote:
Hi everyone,
I'm using OpenStack Mitaka (which deployed from Fuel 9.2) and doing GPU
things.
I got a problem is I need to delete current instance which contains GPU
to release device if I want assign GPU to another new instance temperately.
I'll got
Hi Eddie,
One way to do this is to “shelve” the instance which will allow to use your PCI
device for other instance.
But you won’t be able to “unshelve” the previous instance until you delete or
unshelve the newly created instance.
NOTE:
Shelving will release all the resources associated to tha
Hi everyone,
I'm using OpenStack Mitaka (which deployed from Fuel 9.2) and doing GPU
things.
I got a problem is I need to delete current instance which contains GPU to
release device if I want assign GPU to another new instance temperately.
I'll got "No valid host was found" if I creating new in
> The instance can also be migrated between 2 Westmere hosts.
> As I outline in another email, I suspect (perhaps incorrectly) as the VM has
> "cpu mode='host-model'" in its running config,
> libvirt may be comparing source and destination host CPUs and not guest and
> destination CPUs.
Indeed
On 04.07.2017 17:13, rag.open@openmailbox.org wrote:
> Hi, I have a doubt regarding the upgrade of openstack, it is possible to
> upgrade from an old version or an updated one without going through the
> intermediate versions.
> Example: kilo to newton
> Or it must be incremental kilo, libert
12 matches
Mail list logo
