midonet repo MIA

[iceinvein]

Eucalyptus installation uses midonet.org repo for installation but it seems they've dropped off the face of the earth and is causing issues with installation. Is there a mirror repo we can use for the following?

name=MidoNet
baseurl=http://builds.midonet.org/midonet-5.2/stable/el7/
enabled=1
gpgcheck=1
gpgkey=https://builds.midonet.org/midorepo.key

[midonet-misc]
name=MidoNet 3rd Party Tools and Libraries
baseurl=http://builds.midonet.org/misc/stable/el7/
enabled=1
gpgcheck=1
gpgkey=https://builds.midonet.org/midorepo.key

Also what's the future for VPC if midonet is gone forever?

[avafloww]

Seconding this. I was looking forward to checking out Eucalyptus, but I can't get it installed now 😢

[stash763]

Are there any plans to fix this?

[obino]

So, Midonet github came back but not the builds. We do have some midonet builds we use internally for our QA and deployments: we are considering to either provide these builds, or to provide some custom builds based on the latest source of midonet. For the long term we are considering the move to a different dependency.

[stash763]

Is there a suggested workaround to use until that is done? Would like to test installing eucalyptus but the installer is broken currently with the midonet website being down.

[flyn-org]

@obino, did anyone capture the SRPMs from the MidoNet repository before it went down? I have a fair amount of packaging experience and I am a Fedora package maintainer, so I could propose them for inclusion in EPEL. Getting the package in EPEL would make them available to us until Eucalyptus migrated to something else.

A cursory look found the use of Gradle. This might be a problem for EPEL, because I do not think CentOS/EPEL ships Gradle.

I did note that the MidoNet Git repository had been stale for a while, which worries me.

[obino]

@flyn-org with midonet still in github I don't think we need the SRPMs, right? We did make a copy of the RPMs to be keep doing new installations and maintenance, but if there was a chance to have a repository somewhere it would make our processes a lot more convenient.

[flyn-org]

@obino, it would be better to have a copy of the SRPMs. Some time in the future something might change, e.g., a library in CentOS, that requires us to refresh the RPMs from the SRPMs. I didn't see any .spec files in https://github.com/midonet/midonet.git. Do you have the SRPMs or .spec files?

Where are the midonet RPMs? Could we put them in the Eucalyptus repository? The permissions on the Eucalyptus repository prevent browsing the repository with a browser. For example, loading this URL causes a 403 error:

http://downloads.eucalyptus.cloud/software/eucalyptus/5/rhel/7/x86_64/

[obino]

@flyn-org we do have a way to pull the RPMs from out internal QA. If you pull https://github.com/obino/ats-deploy and use something like ansible-playbook --tags midonet-packages -i inventory.yml playbook_vpcmido.yml you will get the RPMs locally. That's what we have, and it seems that https://github.com/midonet/midonet has the control files for building the RPMs in it.

@stash763 we will update the build to use the same mechanism I pointed above to pull the RPMs down then install them.