[Yahoo-eng-team] [Bug 1786744] [NEW] Cloud-init inject hostname should support dot and without .novalocal
Public bug reported:
Description of problem:
Cloud-init inject hostname should support dot and without .novalocal.
Version-Release number of selected component (if applicable):
cloud-init 0.7.9
How reproducible:
100%
Steps to Reproduce:
1.create a RHEL7.5/7.4 instance specified the hostname with OpenStack API
2.login VM with hostnamectl to check the hostname
Actual results:
API: hostname=ecs-rhel7.4-instance > VM: hostname=ecs-rhel7.novanoval
API: hostname=ecs-rhel74-instance > VM: ecs-rhel74-instance.novanoval
Expected results:
The VM hostname is the same as specified in OpenStack API or ECS Console.
Additional info:
# diff __init__.py
usr/lib/python2.7/site-packages/cloudinit/sources/__init__.py
205c205
< toks = lhost.split(".novalocal")
---
> toks = lhost.split(".")
209c209
< #domain = '.'.join(toks[1:])
---
> domain = '.'.join(toks[1:])
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1786744
Title:
Cloud-init inject hostname should support dot and without .novalocal
Status in cloud-init:
New
Bug description:
Description of problem:
Cloud-init inject hostname should support dot and without .novalocal.
Version-Release number of selected component (if applicable):
cloud-init 0.7.9
How reproducible:
100%
Steps to Reproduce:
1.create a RHEL7.5/7.4 instance specified the hostname with OpenStack API
2.login VM with hostnamectl to check the hostname
Actual results:
API: hostname=ecs-rhel7.4-instance > VM: hostname=ecs-rhel7.novanoval
API: hostname=ecs-rhel74-instance > VM: ecs-rhel74-instance.novanoval
Expected results:
The VM hostname is the same as specified in OpenStack API or ECS Console.
Additional info:
# diff __init__.py
usr/lib/python2.7/site-packages/cloudinit/sources/__init__.py
205c205
< toks = lhost.split(".novalocal")
---
> toks = lhost.split(".")
209c209
< #domain = '.'.join(toks[1:])
---
> domain = '.'.join(toks[1:])
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1786744/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1600701] [NEW] RHEL7.2 OS Login dialog has been covered by cloud-init output logs
Public bug reported: RHEL7.2 OS Login dialog has been covered by cloud-init output logs until user press the "Enter" keyboard, Login appear only after return has been pressed, this affect the user experience. ** Affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1600701 Title: RHEL7.2 OS Login dialog has been covered by cloud-init output logs Status in cloud-init: New Bug description: RHEL7.2 OS Login dialog has been covered by cloud-init output logs until user press the "Enter" keyboard, Login appear only after return has been pressed, this affect the user experience. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1600701/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1489226] [NEW] Nova should support specifying the block devices(/dev/sd*) name to attach to the instance
Public bug reported: nova and horizon dashboard should support that specify the block devices(e.g. /dev/sd*) to attach to an instance. Users can type the block devices(e.g. /dev/sd*) to attach to the instance and the instance can map the block devices(e.g. /dev/sd*) with a symlink(e.g. /dev/sd* - ../../xvd*), and the horizon dashboard can display this symlink relation to users. e.g.: Instance: /dev/sd* - ../../xvd* Dashboard: /dev/sd* vol-xx /dev/xvd* While Amazon EC2 has supported this function very well. In the EC2 Attach Volume dialog box, start typing the name or ID of the instance to attach the volume to in the Instance box, and select it from the list of suggestion options (only instances in the same Availability Zone as the volume are displayed). Device names like /dev/sdh and xvdh are used by Amazon EC2 to describe block devices, the block device mapping is used by Amazon EC2 to specify the block devices to attach to an EC2 instance. Please refer to the following picture for detail. http://www.bogotobogo.com/DevOps/AWS/images/AttachingVolume/AttachVolumeMenu.png http://www.bogotobogo.com/DevOps/AWS/images/AttachingVolume/AttachVolumeDialog.png http://www.bogotobogo.com/DevOps/AWS/images/AttachingVolume/bogo-ami_Instance_with_new_volume.png Best Regards, Sibiao Luo ** Affects: nova Importance: Undecided Status: New ** Description changed: - nova and horizon dashboard should support that specify the block devices(e.g. /dev/vd*) to attach to an instance. Users can type the block devices(e.g. /dev/sd*) to attach to the instance and the instance can map the block devices(e.g. /dev/vd*) with a symlink(e.g. /dev/sd* - ../../xvd*), and the horizon dashboard can display this symlink relation to users. + nova and horizon dashboard should support that specify the block devices(e.g. /dev/sd*) to attach to an instance. Users can type the block devices(e.g. /dev/sd*) to attach to the instance and the instance can map the block devices(e.g. /dev/sd*) with a symlink(e.g. /dev/sd* - ../../xvd*), and the horizon dashboard can display this symlink relation to users. e.g.: Instance: /dev/sd* - ../../xvd* Dashboard: /dev/sd* vol-xx /dev/xvd* While Amazon EC2 has support this function very well. In the EC2 Attach Volume dialog box, start typing the name or ID of the instance to attach the volume to in the Instance box, and select it from the list of suggestion options (only instances in the same Availability Zone as the volume are displayed). Device names like /dev/sdh and xvdh are used by Amazon EC2 to describe block devices, the block device mapping is used by Amazon EC2 to specify the block devices to attach to an EC2 instance. Please refer to the following picture for detail. http://www.bogotobogo.com/DevOps/AWS/images/AttachingVolume/AttachVolumeMenu.png http://www.bogotobogo.com/DevOps/AWS/images/AttachingVolume/AttachVolumeDialog.png http://www.bogotobogo.com/DevOps/AWS/images/AttachingVolume/bogo-ami_Instance_with_new_volume.png Best Regards, Sibiao Luo ** Summary changed: - specify the block devices(/dev/sd*) to attach to an instance + Nova should support specifying the block devices(/dev/sd*) name to attach to the instance ** Description changed: nova and horizon dashboard should support that specify the block devices(e.g. /dev/sd*) to attach to an instance. Users can type the block devices(e.g. /dev/sd*) to attach to the instance and the instance can map the block devices(e.g. /dev/sd*) with a symlink(e.g. /dev/sd* - ../../xvd*), and the horizon dashboard can display this symlink relation to users. e.g.: Instance: /dev/sd* - ../../xvd* Dashboard: /dev/sd* vol-xx /dev/xvd* - While Amazon EC2 has support this function very well. + While Amazon EC2 has supported this function very well. In the EC2 Attach Volume dialog box, start typing the name or ID of the instance to attach the volume to in the Instance box, and select it from the list of suggestion options (only instances in the same Availability Zone as the volume are displayed). Device names like /dev/sdh and xvdh are used by Amazon EC2 to describe block devices, the block device mapping is used by Amazon EC2 to specify the block devices to attach to an EC2 instance. Please refer to the following picture for detail. http://www.bogotobogo.com/DevOps/AWS/images/AttachingVolume/AttachVolumeMenu.png http://www.bogotobogo.com/DevOps/AWS/images/AttachingVolume/AttachVolumeDialog.png http://www.bogotobogo.com/DevOps/AWS/images/AttachingVolume/bogo-ami_Instance_with_new_volume.png Best Regards, Sibiao Luo -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1489226 Title: Nova should support specifying the block devices(/dev/sd*) name
[Yahoo-eng-team] [Bug 1489227] [NEW] Horizon should support specifying the block devices(/dev/sd*) name to attach to the instance
Public bug reported: Dashboard (Horizon) also should support that the same with nova bug: https://bugs.launchpad.net/nova/+bug/1489226 nova and horizon dashboard should support that specify the block devices(e.g. /dev/sd*) to attach to an instance. Users can type the block devices(e.g. /dev/sd*) to attach to the instance and the instance can map the block devices(e.g. /dev/sd*) with a symlink(e.g. /dev/sd* - ../../xvd*), and the horizon dashboard can display this symlink relation to users. e.g.: Instance: /dev/sd* - ../../xvd* Dashboard: /dev/sd* vol-xx /dev/xvd* While Amazon EC2 has supported this function very well. In the EC2 Attach Volume dialog box, start typing the name or ID of the instance to attach the volume to in the Instance box, and select it from the list of suggestion options (only instances in the same Availability Zone as the volume are displayed). Device names like /dev/sdh and xvdh are used by Amazon EC2 to describe block devices, the block device mapping is used by Amazon EC2 to specify the block devices to attach to an EC2 instance. Please refer to the following picture for detail. http://www.bogotobogo.com/DevOps/AWS/images/AttachingVolume/AttachVolumeMenu.png http://www.bogotobogo.com/DevOps/AWS/images/AttachingVolume/AttachVolumeDialog.png http://www.bogotobogo.com/DevOps/AWS/images/AttachingVolume/bogo-ami_Instance_with_new_volume.png Best Regards, Sibiao Luo ** Affects: horizon Importance: Undecided Status: New ** Summary changed: - specify the block devices(/dev/sd*) to attach to an instance + Horizon should support specifying the block devices(/dev/sd*) to attach to an instance ** Summary changed: - Horizon should support specifying the block devices(/dev/sd*) to attach to an instance + Horizon should support specifying the block devices(/dev/sd*) name to attach to the instance ** Description changed: - Dashboard (Horizon) also should support that the same to nova bug: + Dashboard (Horizon) also should support that the same with nova bug: https://bugs.launchpad.net/nova/+bug/1489226 nova and horizon dashboard should support that specify the block devices(e.g. /dev/sd*) to attach to an instance. Users can type the block devices(e.g. /dev/sd*) to attach to the instance and the instance can map the block devices(e.g. /dev/sd*) with a symlink(e.g. /dev/sd* - ../../xvd*), and the horizon dashboard can display this symlink relation to users. - e.g.: - Instance: /dev/sd* - ../../xvd* - Dashboard: /dev/sd* vol-xx /dev/xvd* + e.g.: + Instance: /dev/sd* - ../../xvd* + Dashboard: /dev/sd* vol-xx /dev/xvd* While Amazon EC2 has support this function very well. In the EC2 Attach Volume dialog box, start typing the name or ID of the instance to attach the volume to in the Instance box, and select it from the list of suggestion options (only instances in the same Availability Zone as the volume are displayed). Device names like /dev/sdh and xvdh are used by Amazon EC2 to describe block devices, the block device mapping is used by Amazon EC2 to specify the block devices to attach to an EC2 instance. Please refer to the following picture for detail. http://www.bogotobogo.com/DevOps/AWS/images/AttachingVolume/AttachVolumeMenu.png http://www.bogotobogo.com/DevOps/AWS/images/AttachingVolume/AttachVolumeDialog.png http://www.bogotobogo.com/DevOps/AWS/images/AttachingVolume/bogo-ami_Instance_with_new_volume.png Best Regards, - Sibiao Luo + Sibiao Luo ** Description changed: Dashboard (Horizon) also should support that the same with nova bug: https://bugs.launchpad.net/nova/+bug/1489226 nova and horizon dashboard should support that specify the block devices(e.g. /dev/sd*) to attach to an instance. Users can type the block devices(e.g. /dev/sd*) to attach to the instance and the instance can map the block devices(e.g. /dev/sd*) with a symlink(e.g. /dev/sd* - ../../xvd*), and the horizon dashboard can display this symlink relation to users. e.g.: Instance: /dev/sd* - ../../xvd* Dashboard: /dev/sd* vol-xx /dev/xvd* While Amazon EC2 has support this function very well. In the EC2 Attach Volume dialog box, start typing the name or ID of the instance to attach the volume to in the Instance box, and select it from the list of suggestion options (only instances in the same Availability Zone as the volume are displayed). Device names like /dev/sdh and xvdh are used by Amazon EC2 to describe block devices, the block device mapping is used by Amazon EC2 to specify the block devices to attach to an EC2 instance. Please refer to the following picture for detail. http://www.bogotobogo.com/DevOps/AWS/images/AttachingVolume/AttachVolumeMenu.png http://www.bogotobogo.com/DevOps/AWS/images/AttachingVolume/AttachVolumeDialog.png http://www.bogotobogo.com/DevOps/AWS/images/AttachingVolume/bogo
