Multi Tenancy on Viprions
Hi,
I am not quite sure which forum this questions should go in because it is more about what F5 has in the works for better granular control of partitions in a multi-tenancy environmets. If there is a more suited forum where this should go please let me know.
Our sitation.
We have a pair of BigIPs in house. We have since moved a lot of our kit out into the "private cloud" and our cloud provider uses a pair of Viprions for clients who require BigIP kit. Because we are only one of many of their customers, each customer has their own partition and an account to manage it. What I am finding though is that there are so many restrictions to what we can/can't do which is extremely frustrating when you have full access to your own BigIPs. The main issues that stick out for me are
- the inability to sync changes on our partition (we have to get the provider to do it via their support desk)
- the inability to access the ltm log because there are no partition specifc ltm logs. (I know we can setup a syslog serv and you can use the log statement to log messages to it, but it won't trap tcl and other error types)
- no shell access because it's not restricted to your partition
- cannot install/create SSL certificates, we have to send them to the provider who will then install them.
- cannot backup our config
I am wondering if there are plans within F5 to implement changes so that partitions and all the related files (config files, log files, certs, ect) are stored in their own area so the partition user can be given full access to the files in this partition and have access to more of the management options that are currently blocked becaue they may effect other partition users.
I realise such fundemental changes are not easy to implement, so I am interested to hear if F5 is considering doing this or something like it or "this is as good as it will get".
Also, if I have missrepresented anything or if our provider has provided not quite accurate information to me, please do not hesitate to point these out.
Lastly, this is not a flame aimed at F5 or our provder, I am just interested if F5 have any plans down the line to improve the multi-tenancy functionality.
Regards,
Craig