On 09/03/2010 06:52 AM, Joshua McKenty wrote: > The next step is definitely to write up blueprints of these planned features > (something that I am long overdue to contribute as well). > > I believe we have already had some discussions with RedHat about getting > Fedora Core packages of OpenStack made, I can follow up on this. >
We have some fedora devs working on RPM's for us. So those should be available soon, I'll ping them to find out their status. This should not be a major effort, since we already have Ubuntu packages, in the worst case we could use Alien to convert them. > We will publish a more complete feature list for Austin by the 3rd (e.g., > today!) by completing the missing blueprints. This is absolutely correct. The targeted feature list will be generated using the blueprints and updated through the process. Next Tuesday we have a technical writer joining the project, Anne Gentle, who will help us have much more acceptable documentation. We will be changing the meeting day to Tuesday in the future. I will do my best to find a good time for everyone, but we may end up rotating times so that people in Asia and Australia can more easily participate. I will send an email about the meeting today and blueprints out a little later today. Cheers, Rick > Joshua > > On Fri, Sep 3, 2010 at 6:56 AM, Masanori ITOH <[email protected]> wrote: > >> Hello, >> >> I'm Masanori Itoh of NTT DATA, Japan. >> >> I would like to share some issues on openstack from Japanese >> enterprise system market. >> >> I know that the requirements below do not fit for the austin release >> scheduled in this Octorber, but I believe that still it's useful >> sharing them with folks here. >> >> >> Issue 1. Live Migration support (strong) >> >> From a view point of operating private clouds which host enterprise >> systems, Live Migration is almost mandatory. >> >> Now, we are doing feasibility study to explore if we can do and >> contribute that. >> >> Issue 2. RPM packages (medium) >> >> In Japanese business market, RPM based distributions such as RHEL are >> dominant. So, we would like to have RPM packages too in addition to >> deb packages. >> As for the initial target distribution, Fedora 13 would be appropriate >> I think, and I guess that it's possible we contribute somehow from >> this point too. >> >> Issue 3. Feature list of the austin release >> >> My boss asked me if there is a detailed list of features >> covered by the austin release. >> For example, the list is preferable to have coverage list of >> the Amazon API and Rackspace API which Nova supports. >> >> Is there that kind of list? >> # I'm afraid no... :( >> >> >> BTW, cloud anyone tell me what I should do next? >> >> - Opening blueprint pages? >> >> - Joining the next release IRC? >> - Please understand that the weekly release meeting is 5:00AM of Saturday >> in Japan unfortunatelly ... :( >> >> Thanks in advance, >> Masanori >> >> --- >> Masanori ITOH R&D Headquarters, NTT DATA CORPORATION >> e-mail: [email protected] >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~openstack >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> > > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
