Search results
Create the page "Come" on this wiki! See also the search results found.
- documentation processes, learn about the tools, or report a doc bug, feel free to come by the IRC channel at #openstack-doc at any time. You can also open discussions2 KB (245 words) - 18:11, 12 December 2018
- pleased to host 2nd PRC OpenStack hackathon ! Come to join other OpenStackers to make Liberty a grand success! Come to build your personal network. Learn tips3 KB (447 words) - 01:40, 6 August 2015
- potentially with relationship to Neutron's own objects, but would still come from our API description TBD TBD https://jira.opnfv.org/browse/NETREADY-264 KB (0 words) - 14:48, 12 September 2017
- required for TC governed projects. It is understood that for some IRC does not come with enough features by default and programming a bot to offer additional3 KB (441 words) - 20:57, 7 August 2020
- A bug report in Nova should come pretty close to this: Description =========== Some prose which explains more in detail what this bug report2 KB (234 words) - 14:20, 24 September 2021
- and Intel are pleased to host a hackathon ! Come join other OpenStackers to make Kilo a grand success! Come build your personal network. Learn tips and1 KB (154 words) - 02:09, 13 August 2016
- development is on supporting core-use-cases and deployment strategies as they come from real-world customers and clients deploying OpenStack + VMware technologies3 KB (372 words) - 23:32, 4 September 2013
- followed by provider-specific fields configuration. More Deploy engines are to come in future releases, namely deploy engines for FUEL, Tripple-O etc. Stay tuned3 KB (325 words) - 09:27, 19 May 2014
- people so that they will come to your presentation afterwards. There will be a grid posted on a wall at the Summit... First come, first serve. Dave Walker3 KB (334 words) - 16:32, 24 March 2015
- people so that they will come to your presentation afterwards. There will be a grid posted on a wall at the Summit... First come, first serve. Dave Walker2 KB (287 words) - 16:32, 24 March 2015
- investigating how we might use it more broadly. Like OpenStack, Horizon has come a long way, but still has a long way to go. We expect to get there, but we3 KB (348 words) - 20:51, 3 September 2014
- Attend this meeting, or read the logs to stay up to date. Work items often come up that you can volunteer to take on, or at least offer to help the person7 KB (1,117 words) - 15:09, 13 June 2019
- Use the following draft versions and update the table accordingly. If you come across an issue, search for an existing bug on Launchpad and open a new bug10 KB (491 words) - 09:01, 10 December 2015
- Neutron Networking, and VPC style set ups, where access to the DNS server would come from trusted networks (eg, in-cloud - owned instances, and VPN'd onsite resources)3 KB (303 words) - 17:40, 17 February 2014
- presentations, with the following aims: Gather feedback on the issues that come up in running OpenStack and work to communicate this throughout the community24 KB (3,338 words) - 23:24, 13 June 2022
- things to watch out for during code reviews. Please update this list as you come across new ones. Docstrings are updated if needed Commit messages reflect501 bytes (74 words) - 20:19, 10 November 2014
- for the last 3 months? - For everyone: Cake. Update on exciting things to come in the world of StoryBoard - We have plans, dreams, and a fine selection964 bytes (147 words) - 14:00, 15 January 2016
- content lives will likely depend on the nature of the content. Contributions come in the form of the deliverables above. 1. To contribute feedback: 2. To6 KB (670 words) - 17:19, 27 March 2017
- constraints)For example, a resource may be of resource type volume. It may come from a specific Cinder endpoint registered in Keystone. It may have the1 KB (146 words) - 05:04, 5 May 2014
- practices for porting packages to Yocto. Litao, and Stephen are using this to come up to speed. Jackie: K8s: 1.13.5, working on Anaconda installer. Babak516 bytes (84 words) - 01:30, 25 July 2019
