Thanks Geoff. In the end I was unable to use Brooklyn for my project because the clinical security requirements of the servers was such that the IT dept didn't want to open up the extra ports needed, and every ssh call required 2FA with a special telephone app. I was hoping to change that, but for now, I can't. Brooklyn would have been ideal. I have about 24 processes scattered over various machines.
On Sun, Dec 1, 2019 at 6:14 AM Geoff Macartney <[email protected]> wrote: > Good suggestion Peter. Again, it might be a bit large to undertake before > a 1.0.0? Maybe a 1.0.1? > > What do you think? > > Geoff > > > On Thu, 28 Nov 2019 at 16:33, Peter Abramowitsch <[email protected]> > wrote: > > > Thanks Ludovic > > I'm not a deeply experienced user, but found a problem that I couldn't > see > > as reported or resolved on Jira. It could be I am using the wrong > keywords > > to search for it. Or perhaps it's not considered a bug. > > > > However here's how I would describe it. > > > > When developing a blueprint for a custom entity or an app, one naturally > > goes through a lot of version uploads. When one finally reaches a stage > > that might correspond to an 1.0.0, one naturally would like to delete ALL > > those very early versions and start over. However, through the UI at > > least, I can't seem to do that. Sometimes it prevents me from deleting > the > > very last version of an entity. Or sometimes it looks as if it is > > completely deleted, but when you try to upload a 1.0.0 over again, it > says > > that the version number has already been used. At this point, using > Karaf > > commands I can track down the BOM corresponding to this, but after > issuing > > the delete from there, Brooklyn still seems to remember the entity > > versioning somewhere. All of this should handled cleanly from the UI so > > one can really remove all traces of an entity and start over. > > > > Peter > > > > > > On Thu, Nov 28, 2019 at 3:04 AM Ludovic Farine <[email protected]> > wrote: > > > > > Hi everyone, > > > > > > Hope you are all doing well! > > > > > > Christmas is fast approaching and well hopefully a gift we would all > like > > > to have: Brooklyn 1.0.0 release :) Geoff would be pleased to hear! > > > > > > Working towards this goal of first official release, these are a few > bug > > > fixes and improvements that I believe are worth considering > > (non-exhaustive > > > and not ordered wishlist!) : > > > > > > Bug fixes: > > > > > > - > > > > > > Broken icon links for ELK and DNS entities > > > - > > > > > > REST API Swagger error > > > - > > > > > > Two different versions of jetty-server > > > - > > > > > > Karaf version bump > > > > > > > > > Improvements: > > > > > > - > > > > > > Session Management: introduce expiry settings for inactivity or > > repeated > > > background API calls > > > - > > > > > > User Experience: blueprints ordered by date deployed, cookies to > > > remember preferred sort criteria and palette preferences > > > > > > > > > Clean-up: > > > > > > - > > > > > > Review existing open Pull Requests > > > - > > > > > > Fix most of the Jenkins tests > > > > > > > > > What are your thoughts on this scope? Any other suggestions you would > > like > > > to deliver in this next release? > > > > > > Looking forward to get the community engaging in the next weeks and > > months. > > > > > > Remember you can participate with others on the official Slack channel > > > *#brooklyn* on the official Apache group. Sign up here > > > https://s.apache.org/slack-invite to join the discussion! > > > > > > Thanks > > > > > > Ludo > > > > > > > > > -- > > > > > > Ludovic Farine > > > > > > Senior Technical Project Manager > > > > > > > > > Cloudsoft <https://cloudsoft.io/> | Bringing Business to the Cloud > > > > > > E: [email protected] > > > > > > T: +44 7584 748013 > > > > > > L: https://www.linkedin.com/in/ludovicfarine/ > > > > > >
