ooi team mailing list archive
-
ooi team
-
Mailing list archive
-
Message #00000
Moving away from nova-api binary
-
To:
ooi@xxxxxxxxxxxxxxxxxxx
-
From:
Álvaro López García <aloga@xxxxxxxxxxxxxx>
-
Date:
Thu, 4 Aug 2016 11:35:21 +0200
-
Ironport-phdr:
9a23:vHEMaBMkJHtWZDMgIEMl6mtUPXoX/o7sNwtQ0KIMzox0KPj4rarrMEGX3/hxlliBBdydsKMczbqM+Pi8EUU7or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6anHS+4HYoFwnlMkItf6KuS9aU3578j7z60qaQSj0AvCC6b7J2IUf+hiTqne5Sv7FfLL0swADCuHpCdrce72ppIVWOg0S0vZ/or9YwuxhX7vUm9uZEUL7mZOI8RKFeBzQ+Omxz4sD35jfZSg7aT38CW38RpT7TGwXX2z7zRJx0u2Ouv+561yCyPMP9RPYpXzWp5qEtRQS+23RPDCIw7GyC0p84t6lcuh/0/xE=
-
User-agent:
Mutt/1.5.24 (2015-08-30)
Dear ooiers,
moving forward with ooi I think it is worth to stop using nova-api for
running our interface, and create our own standalone binary and service
(e.g. ooi-api or something like that).
This way we would benefit from having our own configuration (i.e.
nova.conf) and paste (i.e. api-paste.ini) files, remaining completely
independent from the nova installation, so there would be no need to
patch the installation whenever an update takes place. Moreover, this
will ease the installation with devstack, thus we would be able to
implement integration testing more easily with the OpenStack CI (and
even run Rally jobs).
If you agree we can start discussing all the different possibilities for
implementing it.
Cheers,
--
Álvaro López García aloga@xxxxxxxxxxxxxx
Instituto de Física de Cantabria http://alvarolopez.github.io
Ed. Juan Jordá, Campus UC tel: (+34) 942 200 969
Avda. de los Castros s/n skype: aloga.csic
39005 Santander (SPAIN)
Follow ups