Difference between revisions of "Meetings/Ironic"
< Meetings
(→Weekly Ironic Project Team Meeting) |
(→Agenda for next meeting) |
||
| Line 26: | Line 26: | ||
*** decided that clients will do something like POST '{"foo": "bar"}' /nodes/1/vendor_passthru/<method> | *** decided that clients will do something like POST '{"foo": "bar"}' /nodes/1/vendor_passthru/<method> | ||
**** where method doesn't exist in the api code | **** where method doesn't exist in the api code | ||
| − | **** allow POST | + | **** allow POST and GET |
**** rpc side? general 'notify' or single 'passthru' method? | **** rpc side? general 'notify' or single 'passthru' method? | ||
***** single passthru | ***** single passthru | ||
**** what should it return? | **** what should it return? | ||
***** return something like 202 and say that the request is fine but it is async so there's no ret value | ***** return something like 202 and say that the request is fine but it is async so there's no ret value | ||
| + | ***** use GET to retrive status | ||
**** we are not introspecting the user data at all! | **** we are not introspecting the user data at all! | ||
***** only driver should veryfy data | ***** only driver should veryfy data | ||
| + | ***** should data have any requirments / limits? (ie. size < 1k, must be json, etc..) | ||
* Food For Thought: | * Food For Thought: | ||
** How will Ironic handle networking / Ip's | ** How will Ironic handle networking / Ip's | ||
Revision as of 15:59, 28 August 2013
Weekly Ironic Project Team Meeting
If you're interested in bare metal deployments with OpenStack, please join us. This meeting is where we'll talk about the Ironic project, an evolution of the Nova Baremetal driver. Anyone is welcome to add items to the agenda below, or bring up their topic during the open discussion at the end of each meeting.
Meetings are held in the #openstack-meeting room on irc.freenode.net at 19:00 UTC on Mondays. The next meeting is scheduled for September 2th, 2013 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20130902T1900).
Following this meeting is the TripleO team meeting, which often also discusses issues related to bare metal deployments.
Agenda for next meeting
- Improvements of testing
- Outstanding or in-progress tasks:
- API discussion:
- PUT vs PATCH in the API (PUT AND PATCH)
- Review 42690
- vendor_passthru: return values and HTTP methods allowed for this resource
- decided that clients will do something like POST '{"foo": "bar"}' /nodes/1/vendor_passthru/<method>
- where method doesn't exist in the api code
- allow POST and GET
- rpc side? general 'notify' or single 'passthru' method?
- single passthru
- what should it return?
- return something like 202 and say that the request is fine but it is async so there's no ret value
- use GET to retrive status
- we are not introspecting the user data at all!
- only driver should veryfy data
- should data have any requirments / limits? (ie. size < 1k, must be json, etc..)
- decided that clients will do something like POST '{"foo": "bar"}' /nodes/1/vendor_passthru/<method>
- PUT vs PATCH in the API (PUT AND PATCH)
- Food For Thought:
- How will Ironic handle networking / Ip's
- Use models instead of migrations for creating a DB.
- Keystone options not reflected in sample.conf Missing Options
- Inform node of ironic's api url?
- Kernel param
- Dhcp option tag
- Dns name
- Other?
- open discussion
