[Openstack] [Fuel] How to set bonding included admin network by using network template?

Hi everyone, I'm using Fuel community 11 to install Openstack, and I'm using network template to set the network for my own reason. I tried to set bonding with 2 NICs, and bonding mode is 6 (blanace-alb). Then planned all networks going to do tagged VLAN except PXE network, and all networks are

Re: [Openstack] [Fuel] storage question. (Fuel 10 Newton deploy with storage nodes)

Hi Can you describe your disk configuration and partitioning? 2017-09-02 4:57 GMT+08:00 Jim Okken : > Hi all, > > > > Can you offer and insight in this failure I get when deploying 2 compute > nodes using Fuel 10, please? (contoller etc nodes are all deployed/working) > > > >

Re: [Openstack] [Fuel] storage question. (Fuel 10 Newton deploy with storage nodes)

Hi Jim, "Ceph RBD for ephemeral volumes (Nova)" means put Nova ephemeral on the CEPH. That means all VM will use network as vHD I/O on the CEPH cluster. If you're not select it, Nova ephemeral will put on the local disk of compute node. (For example, if instance created at "node-1" compute node,

Re: [Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

platform. As this result, I think I can't take a risk to use this patch, only I can do is waiting for update. Nevertheless, it's still a good experience to know deeper about the operation mechanism on Nova. Appreciate, Eddie. 2017-07-11 9:22 GMT+08:00 Eddie Yen <missile0...@gmail.com>: > Oop

Re: [Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

ithub.com/openstack/nova/blob/master/nova/db/ > sqlalchemy/models.py#L1411 > > [3-] - https://review.openstack.org/#/c/426243/ > > > > *From:* Eddie Yen [mailto:missile0...@gmail.com] > *Sent:* Tuesday, July 11, 2017 3:18 AM > *To:* Jay Pipes <jaypi...@gmail.com> >

Re: [Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

with your > situation. According to the code, the non-existing PCI device should be > removed from the pci_devices table when the PCI manager notices the PCI > device is no longer on the local host... > > On 07/09/2017 08:36 PM, Eddie Yen wrote: > >> Hi there, >> >>

Re: [Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

Hi there, Does the information already enough or need additional items? Thanks, Eddie. 2017-07-07 10:49 GMT+08:00 Eddie Yen <missile0...@gmail.com>: > Sorry, > > Re-new the nova-compute log after remove "1002:68c8" and restart > nova-compute. >

Re: [Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

Sorry, Re-new the nova-compute log after remove "1002:68c8" and restart nova-compute. http://paste.openstack.org/show/qUCOX09jyeMydoYHc8Oz/ 2017-07-07 10:37 GMT+08:00 Eddie Yen <missile0...@gmail.com>: > Hi Jay, > > Below are few logs and information you may want to c

Re: [Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

pci_alias = { "product_id":"0ff3", "vendor_id":"10de", "device_type": "type-PCI", "name":"k420" } nova-compute log shows resource tracker report node only have "10de:0ff3" PCI resource http://paste.openstack.org

Re: [Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

from when > you removed the GPU and restarted the nova-compute service and paste those > logs to paste.openstack.org? Would be useful in tracking down this buggy > behaviour... > > Best, > -jay > > On 07/06/2017 08:54 PM, Eddie Yen wrote: > >> Hi Jay, >>

Re: [Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

Hi Jay, The status of the "removed" GPU still shows as "Available" in pci_devices table. 2017-07-07 8:34 GMT+08:00 Jay Pipes <jaypi...@gmail.com>: > Hi again, Eddie :) Answer inline... > > On 07/06/2017 08:14 PM, Eddie Yen wrote: > >> Hi everyo

[Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

Hi everyone, I'm using OpenStack Mitaka version (deployed from Fuel 9.2) In present, I installed two different model of GPU card. And wrote these information into pci_alias and pci_passthrough_whitelist in nova.conf on Controller and Compute (the node which installed GPU). Then restart

Re: [Openstack] [OpenStack] [nova] How can I release PCI device resources without delete instance?

-compute(Compute) But when I check MySQL, the GPU info which I already removed still in pci_devices table. I remember there's a bug about this case but it already fixed. How can I fix this issue? Thanks, 2017-07-06 11:42 GMT+08:00 Eddie Yen <missile0...@gmail.com>: > Tha

Re: [Openstack] [OpenStack] [nova] How can I release PCI device resources without delete instance?

hen 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" <missile0...@gmail.com> wrote: > >> Hi, thanks for reply first! >> >> After

Re: [Openstack] [OpenStack] [nova] How can I release PCI device resources without delete instance?

m that may cause application atypical. I'll try how to make my application not to rely on a persistent IP. Thanks, Eddie. 2017-07-05 19:36 GMT+08:00 Jay Pipes <jaypi...@gmail.com>: > On 07/05/2017 04:18 AM, Eddie Yen wrote: > >> Hi everyone, >> >> I'm using OpenSt

[Openstack] [OpenStack] [nova] How can I release PCI device resources without delete instance?

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

Re: [Openstack] [OpenStack] [Fuel] Packing kernel drivers into target image.

repository, and rebuild the repo (to update > metadata about the packages). > > 1st option is more preferable, it would simplify for you further upgrades. > > Thanks, > > On Tue, Feb 7, 2017 at 5:35 PM, Eddie Yen <missile0...@gmail.com> wrote: > >> Hi Evgeniy, than

Re: [Openstack] [OpenStack] [Fuel] Packing kernel drivers into target image.

nailgun/targetimages", > in this case don't forget to update checksums in > "env_1_ubuntu_1404_amd64.yaml" file. > > Thanks, > > [1] https://docs.mirantis.com/openstack/fuel/fuel-9.1/ > reference-architecture/single/index.html > > On Sun, Feb 5, 2017 at 11:42 PM, Eddi

[Openstack] [OpenStack] [Fuel] Packing kernel drivers into target image.

Hi everyone, I'm using Fuel 9.1 to deploy OpenStack, but I found that the kernel still too old to support Intel i219-LM NIC card. So I'm followed the instruction from OpenStack Documents and built the bootstrap kernel with latest e1000e driver. Then tested and it successfully catch i219-LM

[Openstack] How to build kernel driver for Fuel bootstrap image?

Hello everyone. I had a motherboard which contains 3 x Intel I210 and 1 x Intel i219-LM network adapter. Trying to deploy this machine as compute node by using Fuel 7.0, but found that CentOS bootstrap can't recognize i219-LM. So I'm trying to build a new "e1000e" kernel driver which can

Re: [Openstack] How to expand /boot size in Fuel deployment?

estart > > Then add another node to the cluster, it should have 300M /boot partition. > > > [1] > https://github.com/openstack/fuel-web/blob/stable/7.0/nailgun/nailgun/extensions/volume_manager/manager.py#L810 > > Vladimir Kozhukalov > > On Wed, May 25, 2016 at

[Openstack] How to expand /boot size in Fuel deployment?

Hi everyone, this is my first time ask questions to this mailing list. Apologize first that I'm not good at English. I'll try to ask the question on English clearly. Welcome to ask if I got nay details that I'm not write it clear. I'm using Fuel 7.0 to deploy my OpenStack environment (Kilo, of