Get all cookbooks (Juno) working on Ubuntu trusty (14.04)
I've just tried an AIO converge and it fails. Two issues are immediately visible:
- OpenStack packages do not have init scripts in /etc/init.d, which causes chef to error out when trying to enable the service (some services like rabbitmq still have an initscript (not linked to /lib/init/
- We seem to add the openstack-ppa repo, but this is unnecessary for trusty
-- 07/17/2014 --
Pushing this to Juno Series (j^2, markvan, galstrom)
Blueprint information
- Status:
- Complete
- Approver:
- Justin Shepherd
- Priority:
- Essential
- Drafter:
- Matt Thompson
- Direction:
- Approved
- Assignee:
- Mark Vanderwiel
- Definition:
- Approved
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Mark Vanderwiel
- Completed by
- Mark Vanderwiel
Related branches
Related bugs
| Bug #1313646: Wrong Chef::Provider::Service in Ubuntu 14.04 | Won't Fix |
| Bug #1396908: [network] route must have ip information | Fix Released |
Sprints
Whiteboard
https:/
https:/
http://
https:/
----
I spent some more time looking into this today, and found that:
- Ubuntu have no intention of creating init scripts for their OpenStack packages
- Chef look to be moving Ubuntu 13.10+ to use Upstart service provider (https:/
- rabbitmq-server doesn't have an upstart script, and the actual service is managed in the rabbitmq cookbook which we have no control over
- running the cookbook as is on 14.04 fails when we update openstack-common cookbook as rabbitmq defaults job_control attribute to "initd" and has init.d start/stop_commands but no associated init.d enable/
- this can be fixed by either changing rabbitmq job_control attribute to "upstart" (works, but feels dirty as it actually deletes the package's /etc/init.
- apache2 suffers a similar fate in that Ubuntu provide no upstart script and the package is actually managed in the apache2 cookbook (the cookbook overrides restart/
Not entirely sure how we proceed here.
---
Issues in other cookbooks:
- apache2 https:/
- rabbitmq https:/
Based upon the above, is this work slated for icehouse, or could be pushed into Juno?
---
Bug related to this: https:/
---
Monkey patch that might be useful while other cookbooks are updated.
if node[:platform] == 'ubuntu' && node[:platform_
['keystone'
svc = resources(service: monkey_patch)
svc.
end
end
UPDATE 11/14:
As of RC1 of the chef 12 client, monkeypatches are no longer needed.
I've noticed that python-
Ubuntu 14.04 ships with Apache2.4 by default. This completely breaks the dashboard cookbook since it has a reliance on the apache2 cookbook < v2.0
UPDATE 11/27:
here you can find a starting point for working on/testing the juno-14.04 thingies
https:/
- nova network is confirmed working
- there is an issue with block storage (have to have look what)
- currently checking neutron
Gerrit topic: https:/
Addressed by: https:/
Trusty juno updates
Addressed by: https:/
Trusty juno updates
Addressed by: https:/
Trusty juno updates
Addressed by: https:/
Trusty juno updates
Addressed by: https:/
Trusty juno updates
Addressed by: https:/
Trusty juno updates
Addressed by: https:/
Trusty juno updates
Addressed by: https:/
Trusty juno updates
Addressed by: https:/
Trusty juno updates
Addressed by: https:/
Trusty juno updates
Addressed by: https:/
Trusty juno updates
Addressed by: https:/
Trusty juno updates
Addressed by: https:/
Trusty juno updates
Addressed by: https:/
MySql cookbook ver 6 changes
Addressed by: https:/
MySql cookbook ver 6 changes
Work Items
Work items:
infra change to allow our rake tests to run: DONE
infra change to allow trusty, chef 12, chef dk to run our rake tests (Jan): POSTPONED
infra change to allow existing/old stable branches to continue to use old gates without rake: POSTPONED
update all Gemfiles to use chef 12: POSTPONED
update all spec helpers to go after trusty: INPROGRESS
update to use mysql ver 6 cookbook: INPROGRESS
