4 ms·
An interesting approach; I'm however skeptic as to how well DevOps lends itself to be visualized. And even if the techniques and products do now, futures ones m
by roeme 12y ago
An interesting approach; I'm however skeptic as to how well DevOps lends itself to be visualized. And even if the techniques and products do now, futures ones may not, or require a lot of work to bring into this.
>VisualOps is created with a goal of both "easy to understand" and "total control".
I don't know, this seems almost too ambitious to me. I'm wary of car analogies, but alas: While everyone can drive a car, does this yet qualify as "total control"? Assuming I'd like to control everything about my engine - resulting in a shitload of controls on my dashboard, is that car still easy to understand (to me yes, to my mum, - or a newcomer for that matter - doubtfully so)? And by hiding the additional controls behind a "ADVANCED CONTROLS" cover kinda defeats the "easy to understand" part, how soon until HOWTO's appear whose first instruction is to lift said cover?
I'm sure there are boatloads of loopholes in my analogy, but you get the general idea. Not really sold on the concept, but if somebody can offer insightful comments, I might be convinced. Not easily though.
>Complicated data format Even if someone hacked into our servers, took a copy of the data, stole our soure code or laptop, they still cannot get your information.
Remove this sentence ASAP. It's an insult to everyone with at least a basic grasp on good IT and security principles. wtf; just because it's supposedly complicated a determined adversary cannot break the code?
- michaelmior 12y agoI missed that sentence, but agreed that it should be removed. I don't think "complicated data format" is a good selling point. Quite the opposite really.
- tbronchain 12y agoHi Michael, We are not sure what you means by "I don't think "complicated data format" is a good selling point.", could you tell us more? Thanks!
- michaelmior 12y agoThe FAQ suggests that the fact you use a complicated data format is a good thing and beneficial to security. I really doubt this is true.
- tbronchain 12y agoRight, we have modified this part. By "complicated data format", we actually meant strong encryption algorithm. Sorry for the confusion.
- roeme 12y agoReading this, and skimming over your other comments I suspect that english isn't really your first or second language...consider asking a friend with a english cert above FCE level to help you out with translations. No need for a professional service, but a wee bit better than currently might help you. Because...between "complicated data format" and "strong encryption algorithm", there are not just worlds, but universes. Subsequently, this correction also sounds suspicious to somebody who assumes you are fluent in english (or is used to it).
- tbronchain 12y agoWe'll do, thanks for the advice :)
- tbronchain 12y agoHi Roeme, thank you for your comment! >VisualOps is created with a goal of both "easy to understand" and "total control". We tried or best to associate the easy understanding to full control. I totally understand your point, and this is the idea behind VisualOps: you need to deal with complicated tools if you want to get total control (eg. Chef with OpsWorks), or you need to make some concessions if you want something easy (eg. PaaS platforms like Heroku). With VisualOps, you have a total control of your instances software configuration, as well as the "hardware"/"network" specifications available by AWS. >Complicated data format Even if someone hacked into our servers, took a copy of the data, stole our source code or laptop, they still cannot get your information. I think there is a confusion there. What we meant is that the AWS credentials are store on specific servers, which are not accessible by the employees here. These credentials aren't accessible using data stored on employees computers or internal git repos Thanks for telling us, we will modify this sentence, and sorry for the confusion.