Le vendredi 31 mai 2013, à 15:16 -0500, arkady_kanev...@dell.com a écrit : > Adam, > There are many issues. > First, nobody really tried it for all barclamps. > We tried it with a few ones. And Mirantis tried it on a few ones. > There were a few patches filed for it. > > Main thing that we need to ensure that we are able to specify specific > proposal of a dependency barclamp for deployment of a barclamp. > That means that we should be able to find which node(s) the dependency > proposal runs on. > I am not even sure if we can pull it off on CB1.x code or we need to do on CB > 2.x one. > > I just do not see that we will have any time now to address it with many > higher priority items. > Thus, I want to prevent Consumers to try multi-proposal accidentally. > Luckily, thanks for previous crowbar developers, this is an attribute we can > easily set. > That is what I want to do for now.
For the community branch, I think it'd be more useful to have people test this and and report about bugs instead of just disabling this. I see no reason why this would not be fixable. (Or maybe I'm missing something?) Vincent -- Les gens heureux ne sont pas pressés. _______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
