Mango Lassi Convention: What topics would you like to see
-
That is a good question: Probably a combination but no Marketing people, Technical people only.
-
I know someone who would be willing to help out with the Powershell stuff
In all seriousness, we'd have to find out what level of skill to cater toward, and then work from there. In the other thread, SAM talked about the flow of problem discovery to tool creation and implementation, what's the thought process, how to approach the solution, etc. That'd be a good session, I think.
-
Powershell would be one I'd love! Another one I'd love would be kind of Basics of IT 201. There are a lot of things that I'd like to have a basic better understanding of. What IS a SAN? Why does @scottalanmiller hate them so much? A list of things like ESXi features at each licensing point, and why/when someone would need to go to the next tier. There is a ton of general info that isn't a 101 class, but it still good info I'd love to have an instructor-lead training on.
-
@ajstringham idealistically I like the idea (um, now how do you like ideas except idealistically?) but I wonder what exact material would be included in so broad a class? We could do a Storage 101, I guess. I did a talk on Open Storage at SW 2010 that was very popular. Could take that and broaden it to deal with a larger range of storage subjects I suppose.
-
@scottalanmiller said:
@ajstringham idealistically I like the idea (um, now how do you like ideas except idealistically?) but I wonder what exact material would be included in so broad a class? We could do a Storage 101, I guess. I did a talk on Open Storage at SW 2010 that was very popular. Could take that and broaden it to deal with a larger range of storage subjects I suppose.
Take general topics, like Storage, Virtualization, etc. Now drill down into more advanced basic topics (talk about differences between SANs and NASes as opposed to what is RAID). Make it part history, mostly practicality.
-
@ajstringham that would be many sessions. Giving a 101 of Storage is more than an hour topic. Same for virtualization. It's not like you could take both of those plus several other topics and turn it all into one, one hour or less session to do overviews.
Doing the Open Storage talk was 45 minutes on its own and rather rushed to keep it there, as an example.
-
Maybe a few "101" sessions would make sense then?
You could have a Storage 101 and a Virtualization 101 and maybe even a Linux 101 for people to get a taste of when and where to think about deploying Linux and to get a feel for the state of the Linux ecosystem as it stands today.
-
What about a Backup 101 session? Something that talks about tapes versus disk backups. Grandfather, father, son. Incremental, differential, full. Image versus file system backups. Software versus appliances. A survey of market leaders. Archiving. Storage options for backups. That sort of thing.
-
What about some sessions being neutral (101 classes.) And other sessions being vendor sponsored?
That way a vendor, let's just pick on IBM since they won't likely be there, could sponsor a special session such as:
The Applicability of the Mainframe to the SMB brought to you by IBM
-
I really like the storage discussion options.
A Linux 101 could be good as well
And scripting (something I've always shy'ed away from, but know I should know) 101 and 201.
-
@Dashrender said:
And scripting (something I've always shy'ed away from, but know I should know) 101 and 201.
PowerShell Scripting (Windows) or BASH Scripting (UNIX) or Python Scripting (Generic) or something else?
-
I live in the SMB world... so everything Windows based for me.
Not that I want to be pigeon holed, but I know that would be most helpful to me at this point.
-
@Dashrender said:
I live in the SMB world... so everything Windows based for me.
Not that I want to be pigeon holed, but I know that would be most helpful to me at this point.
I think that a session on why Linux should be in much of the SMB would be good, actually. "Linux: When and Where for the SMB" as it is way more applicable to the SMB than people give it credit for. Especially when the SMB is looking to save money and stay current at the same time.
-
As long as you can do AD type stuff and GPO type stuff with Linux, I'll totally agree with you.
-
@Dashrender said:
As long as you can do AD type stuff and GPO type stuff with Linux, I'll totally agree with you.
Are you thinking of Linux only in the context of a desktop and not as a part of your infrastructure?
-
No, Because of application requirements, mine (and I'm guessing may others) can't leave the Windows desktop (that's not to say many couldn't leave MS behind).
I'm talking servers - I'm fine using Linux on my servers as long as I have a single authentication mechanism for everything, GPOs to push policies to the windows clients, and I know that one linux box will talk to the others just fine.
-
Maybe someone can talk about Linux management, ala Puppet or something else (my Linux-fu is not so good)?
Discuss what's keeping people from using it, and why should you not be afraid of it.
-
@Dashrender said:
I'm talking servers - I'm fine using Linux on my servers as long as I have a single authentication mechanism for everything, GPOs to push policies to the windows clients, and I know that one linux box will talk to the others just fine.
Well installing a Linux box will not break GPOs going to Windows desktops. And Linux will authenticate to AD just fine, Linux can even replace AD and provide GPO management even though it itself is not managed via GPO. No need for GPOs with Linux, you can just use super simple scripts or GPO replacement tools like Chef and Puppet.
-
@scottalanmiller said:
@ajstringham that would be many sessions. Giving a 101 of Storage is more than an hour topic. Same for virtualization. It's not like you could take both of those plus several other topics and turn it all into one, one hour or less session to do overviews.
Doing the Open Storage talk was 45 minutes on its own and rather rushed to keep it there, as an example.
Wasn't saying it would it. They were just general examples of a topic to cover and dive into across multiple sessions.
-
I know that @JaredBusch mentioned in a post on SW how he wished there were more advanced classes offered. Perhaps a 101 and a 201 (or higher) track so that each level could be addressed? Maybe before scheduling, get an idea of who would like to attend which session so that people don't have to make hard choices and miss sessions they really wanted to attend? It's not like we're likely to have 5 sessions running at once at the first ML-Con.
