Forum Discussion
CirrostratusCentral manager - some practical questions
MVPZdenek I can give you answers to some of the questions :-)
Currently there is not any partitions implemented. As everything is based on AS3, where tenant/partition is part of the template, I would expect it to be possible sometime down the road. NEXT has been purposely lightly implemented to remove unused features to make it a more nimble product. If enough push back arises around a feature I believe it will be implemented.
Regarding APM it is just around the corner.
CirrostratusI understand the concept of having all in AS3, but CM will be a UI and not just UI for one LB but probably all in the environment and as central element I would suppose it supports some kind of object organization, now it seems it is like "hey lets put all into one pile and users will deal with that somehow".
Removing stuff is also something, how do you know what's unused? For example we don't send you any data what we use. you have quickfiles from support, but it's still not all. Do not remove too much, reason why we pay F5 is that it's been a "swissknife" and that is not "lightweight" stuff from its nature..
2 questions answered thanks, 5 waiting :)
- lnxgeek
You are right, CM is the king of the castle :-)
I believe that F5 has done a lot of research to figure out what to include and what to remove. I am myself a vivid advocate for the Swiss army knife story, so I understand your take on it.
It is early days, so I'm sure we will have a lot of iterations coming in the next period of time. F5 has historically taken chances on stuff (just look at the iRules - they just guested when they chose to implement it) where they have implemented or changed something without having all the knowledge.
The best you can do is to express your pains here or through your local F5 team, to tell them what we need.
