Difference between revisions of "Meetings/Designate"
< Meetings
(→Agenda) |
|||
| Line 21: | Line 21: | ||
*** Where does this fit in the dependency tree for mdns and server pools | *** Where does this fit in the dependency tree for mdns and server pools | ||
** RecordSets revisited - the url gets very long and hard to follow | ** RecordSets revisited - the url gets very long and hard to follow | ||
| + | ** TenantId in URL. Some of the other openstack services have the TenantID in the URL. Should we too have it in the URL instead of in the context? | ||
| + | *** Cinder - http://api.openstack.org/api-ref-blockstorage.html | ||
| + | *** Nova - http://api.openstack.org/api-ref-compute.html | ||
| + | *** Heat - http://api.openstack.org/api-ref-orchestration.html | ||
| + | |||
* Open Discussion | * Open Discussion | ||
Revision as of 19:43, 18 March 2014
DNSaaS Meetings
The DNSaaS team holds a weekly IRC meeting in #openstack-meeting-alt on Wednesdays at 17:00 UTC
Meeting logs are available at http://eavesdrop.openstack.org/meetings/designate/
Next meeting
Date of next meeting Wednesday 19 March, 17:00 UTC
Agenda
- Review action items from last week (See Meeting Logs for previous week)
- Specific Items:
- MiniDNS Blueprints and Work Items
- "Master" blueprint - https://blueprints.launchpad.net/designate/+spec/mdns-master
- Wiki Blueprint, with steps listed - https://wiki.openstack.org/wiki/Designate/Blueprints/MiniDNS
- Pre-Wiki translation of "Implementation Steps" that's much easier to read: LINK TODO
- Records Table Redesign blueprint
- Where does this fit in the dependency tree for mdns and server pools
- RecordSets revisited - the url gets very long and hard to follow
- TenantId in URL. Some of the other openstack services have the TenantID in the URL. Should we too have it in the URL instead of in the context?
- MiniDNS Blueprints and Work Items
- Open Discussion
Future meetings
Possible Agenda Topics:
- Incubation ReDiscussion (Delay to post TC policy changes)
- Incubation Vote
