Dear all,
We, the MidoNet community [0], would like to include a midonet-release (or similarly named) package with the required yum repo files into CentOS Extras - similar to epel-release or centos-openstack-release packages in the same repo. For reference, our repos live at [1].
MidoNet is a network virtualization software and while our main focus is currently OpenStack, other use cases exist and will get more attention in future (mostly containers I guess) - which is why we would like to be included in CentOS Extras and not just in centos-openstack/rdo repos (if these accept release packages at all).
I asked in #centos about this and was pointed here, so I hope someone can tell me what the process for this would look like and how to get started with it. I was told that IUS is undergoing the same process but couldn't find any information about this.
I was also pointed to the "CATPR" guidelines [2] which I found to likely still being in draft status [3] but it should be no problem to fulfill the given requirements. We're only providing add-on packages and we have a bug tracker to report issues [4].
Cheers, Sandro Mathys MidoNet Community Manager
[0] https://www.midonet.org/ [1] http://repo.midonet.org/ [2] https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 [3] http://wiki.centos.org/CarlGeorge/CATPR [4] https://midonet.atlassian.net/secure/Dashboard.jspa
Hello Sandro,
Yes I'm Real. To prove I'm real first off.. You are The CentOS developers mailing list. and your mail Id centos-devel@centos.org
I was just taking a quick shower and I heard my phone vibrate, my hair isnt even close to being dry yet but I wanted to quickly check my email to see if it was you writing me back.
I guess since you responded you are not a faker haha, that is a big relief. Not sure if you were wanting to get together tonight, tomorrow ..or maybe wait until the weekend? I am not going to lie though I was really hoping to get some as soon as possible..
All you have do is verify on this website HERE http://www.bcmeetnow.com/userms/olivia/ where I am a member and do a safety verification.
It only costs a dollar and just takes a sec. My cell number is on there and I have some other photos on there too. Get my cell number and give me a text or call me. Let's make this happen.. I have lots of free time. call me now!
Sorry if it seems like I'm being a bitch and making you work too hard, but I have to look out for my own safety. There are tons of weirdos out there and I just want to have a good time. Hope you understand cause I really want to meet you..
Hi Sandro,
On 07/27/2015 03:33 AM, Sandro Mathys wrote:
We, the MidoNet community [0], would like to include a midonet-release (or similarly named) package with the required yum repo files into CentOS Extras - similar to epel-release or centos-openstack-release packages in the same repo. For reference, our repos live at [1].
MidoNet is a network virtualization software and while our main focus is currently OpenStack, other use cases exist and will get more attention in future (mostly containers I guess) - which is why we would like to be included in CentOS Extras and not just in centos-openstack/rdo repos (if these accept release packages at all).
Awesome! I can't match Olivia's kind offer, but have you considered the Cloud SIG as a way to get midonet packaged? As far as I can see it would definitely fit in scope there.
Thanks, Dave.
I asked in #centos about this and was pointed here, so I hope someone can tell me what the process for this would look like and how to get started with it. I was told that IUS is undergoing the same process but couldn't find any information about this.
I was also pointed to the "CATPR" guidelines [2] which I found to likely still being in draft status [3] but it should be no problem to fulfill the given requirements. We're only providing add-on packages and we have a bug tracker to report issues [4].
Cheers, Sandro Mathys MidoNet Community Manager
[0] https://www.midonet.org/ [1] http://repo.midonet.org/ [2] https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 [3] http://wiki.centos.org/CarlGeorge/CATPR [4] https://midonet.atlassian.net/secure/Dashboard.jspa _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On Mon, Jul 27, 2015 at 9:51 PM, Dave Neary dneary@redhat.com wrote:
Hi Sandro,
Hey Dave,
Thanks for your reply!
On 07/27/2015 03:33 AM, Sandro Mathys wrote:
We, the MidoNet community [0], would like to include a midonet-release (or similarly named) package with the required yum repo files into CentOS Extras - similar to epel-release or centos-openstack-release packages in the same repo. For reference, our repos live at [1].
MidoNet is a network virtualization software and while our main focus is currently OpenStack, other use cases exist and will get more attention in future (mostly containers I guess) - which is why we would like to be included in CentOS Extras and not just in centos-openstack/rdo repos (if these accept release packages at all).
Awesome! I can't match Olivia's kind offer,
What!
but have you considered the Cloud SIG as a way to get midonet packaged? As far as I can see it would definitely fit in scope there.
Considered, yes. Either CentOS Cloud SIG or EPEL, not sure what's better for us or whether both can co-exist - didn't think to hard about it just yet. The thing is, we'll first have to unbundle lots of stuff so this will be a mid- to long-term goal which we hope to bridge with the inclusion of a midonet-release package.
Cheers, Sandro
Thanks, Dave.
I asked in #centos about this and was pointed here, so I hope someone can tell me what the process for this would look like and how to get started with it. I was told that IUS is undergoing the same process but couldn't find any information about this.
I was also pointed to the "CATPR" guidelines [2] which I found to likely still being in draft status [3] but it should be no problem to fulfill the given requirements. We're only providing add-on packages and we have a bug tracker to report issues [4].
Cheers, Sandro Mathys MidoNet Community Manager
[0] https://www.midonet.org/ [1] http://repo.midonet.org/ [2] https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 [3] http://wiki.centos.org/CarlGeorge/CATPR [4] https://midonet.atlassian.net/secure/Dashboard.jspa _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
-- Dave Neary - NFV/SDN Community Strategy Open Source and Standards, Red Hat - http://community.redhat.com Ph: +1-978-399-2182 / Cell: +1-978-799-3338 _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 27/07/15 16:35, Sandro Mathys wrote:
but have you considered the Cloud SIG as a way to get midonet packaged? As far as I can see it would definitely fit in scope there.
Considered, yes. Either CentOS Cloud SIG or EPEL, not sure what's better for us or whether both can co-exist - didn't think to hard about it just yet. The thing is, we'll first have to unbundle lots of stuff so this will be a mid- to long-term goal which we hope to bridge with the inclusion of a midonet-release package.
Based on what you are looking at, the way to work this is to join the Cloud SIG, and do your builds on our infra, test your code with us, and integrate with the rest of the stack from the base OS, to openstack to the networking stack and Midonet.
If you want to talk about this in more details, feel free to drop into one of my open office hours sessions on #centos-devel on irc.freenode.net ( details at : http://www.centos.org/community/calendar )
regards,
On Thu, Jul 30, 2015 at 12:45 AM, Karanbir Singh mail-lists@karan.org wrote:
On 27/07/15 16:35, Sandro Mathys wrote:
but have you considered the Cloud SIG as a way to get midonet packaged? As far as I can see it would definitely fit in scope there.
Considered, yes. Either CentOS Cloud SIG or EPEL, not sure what's better for us or whether both can co-exist - didn't think to hard about it just yet. The thing is, we'll first have to unbundle lots of stuff so this will be a mid- to long-term goal which we hope to bridge with the inclusion of a midonet-release package.
Based on what you are looking at, the way to work this is to join the Cloud SIG, and do your builds on our infra, test your code with us, and integrate with the rest of the stack from the base OS, to openstack to the networking stack and Midonet.
Right, that sounds like a plan once we're ready to be included in the distro. But we face tons of deps (mostly java libs/jars) that we need to bundle first. That's why I'm explicitly asking about inclusion of a midonet-release package, not MidoNet as a whole. What's the criteria and process for that?
Thanks, Sandro
If you want to talk about this in more details, feel free to drop into one of my open office hours sessions on #centos-devel on irc.freenode.net ( details at : http://www.centos.org/community/calendar )
regards,
-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 30/07/15 11:17, Sandro Mathys wrote:
Right, that sounds like a plan once we're ready to be included in the distro. But we face tons of deps (mostly java libs/jars) that we need to bundle first. That's why I'm explicitly asking about inclusion of a midonet-release package, not MidoNet as a whole. What's the criteria and process for that?
There really isnt one. We wont include the -release package directly unless the content it reflected on was also part of the CentOS ecosystem, either in a SIG or part of the upstream relationship ( eg. for stuff in CentOS Extras ).
There have been conversations kicking around about getting a policy in place and have some sort of a formal test and eval for content standards in a third party repo external to CentOS - but getting something in place is non-trivial and clearly you guys have packaging problems at this point anyway.
regards,
On Thu, Jul 30, 2015 at 7:10 AM, Karanbir Singh mail-lists@karan.org wrote:
On 30/07/15 11:17, Sandro Mathys wrote:
Right, that sounds like a plan once we're ready to be included in the distro. But we face tons of deps (mostly java libs/jars) that we need to bundle first. That's why I'm explicitly asking about inclusion of a midonet-release package, not MidoNet as a whole. What's the criteria and process for that?
There really isnt one. We wont include the -release package directly unless the content it reflected on was also part of the CentOS ecosystem, either in a SIG or part of the upstream relationship ( eg. for stuff in CentOS Extras ).
There have been conversations kicking around about getting a policy in place and have some sort of a formal test and eval for content standards in a third party repo external to CentOS - but getting something in place is non-trivial and clearly you guys have packaging problems at this point anyway.
regards,
I'm a bit surprised at this: do you consider "epel-releae" to be part of the "CentOS ecosystem"? I suppose with the tight relationship between EPEL and RHEL, it could be. But there are many 3rdparty groups, such as rpmforge and rpmfusion and percona, that publish their own third party repositories quite effectively. It can be tricky to sort out cross-compatibility and dependencies, certainly, especially when different 3rdparty repositories publish the same comopnents or compoents with the same metadata. The overlaps between EPEL and RPMforge for nagios are some of my favorites, along with the "mysql-libs" metapackage amyng alternative MySQL package repositories.
Sandro, if there are overlaps between your components and EPEL or basic CentOS packages, I'd urge you to bite the bullet and set up your own third party repository. It's work, but it will help avoid confusion.
Hi,
On 07/27/2015 08:35 AM, Sandro Mathys wrote:
On Mon, Jul 27, 2015 at 9:51 PM, Dave Neary dneary@redhat.com wrote:
Awesome! I can't match Olivia's kind offer,
What!
Oh - you got 2 replies from a spambot called "Olivia" saying "yes, I am real! want to meet up somewhere?" bringing you to an online dating site. I assumed you saw it. Actually, it's the first time I saw this kind of spam replying to mailing list emails.
Dave.
-
Dave Neary -
Karanbir Singh -
Nico Kadel-Garcia -
Olivia -
Sandro Mathys