Clint, do you mean * use os-collect-config and its HTTP transport as a base for the PoC or * migrate os-collect-config on PoC after it is implemented on oslo.messaging
I presume the later, but could you clarify? 2013/12/18 Clint Byrum <cl...@fewbar.com> > Excerpts from Dmitry Mescheryakov's message of 2013-12-17 08:01:38 -0800: > > Folks, > > > > The discussion didn't result in a consensus, but it did revealed a great > > number of things to be accounted. I've tried to summarize top-level > points > > in the etherpad [1]. It lists only items everyone (as it seems to me) > > agrees on, or suggested options where there was no consensus. Let me know > > if i misunderstood or missed something. The etherpad does not list > > advantages/disadvantages of options, otherwise it just would be too long. > > Interested people might search the thread for the arguments :-) . > > > > I've thought it over and I agree with people saying we need to move > > further. Savanna needs the agent and I am going to write a PoC for it. > Sure > > the PoC will be implemented in project-independent way. I still think > that > > Salt limitations overweight its advantages, so the PoC will be done on > top > > of oslo.messaging without Salt. At least we'll have an example on how it > > might look. > > > > Most probably I will have more questions in the process, for instance we > > didn't finish discussion on enabling networking for the agent yet. In > that > > case I will start a new, more specific thread in the list. > > If you're not going to investigate using salt, can I suggest you base > your POC on os-collect-config? It it would not take much to add two-way > communication to it. > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
