-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build Communications #11
Comments
Ah you meant @JedMeister! 😄 |
Sounds good. We can move the conversation here then |
Made some changes and doing a build now. This will be the last one until after 6 My time |
Sounds good. I think you are in the East (EST). I am in Colorado (MST). Need to get on some other projects for sure. Would love to have this close to wrapped. I put a few "issues" up we might address. (the ARCH/REL/VER) thing I will take a stab at in dependencies. We need it for Gdata and WHTMLTOX |
How to make a Smile? :) I am guessing, but no. 😄 (colon : sm) and starts to show. OK |
@JedMeister If I "fetch" Common that is temporary. Correct? Doing a Pull is more permanent. |
Fetch will pull the change down to your repo, pull will fetch and merge |
(Updated x 2) Firstboot 2nd Boot. postgres can NOT log in with password set at firstboot inithooks (Was able to by assigning same pw in Webmin Postgresql USER update (postgres) so exact same as yesterday. Perhap the Common Fetch did not work Update #1 Very Long Wait for Odoo. Update #2 Openerp Database is "accessible" to Odoo. However, I do not know the User Login or the Password for it. Normally this would be set in "database creation" but perhaps there is a setting some where defining such. (Some Merit in having an accessible database at start, however.. need to set controls to it as well) I will look in Postgre to see if there is a user in there. There must e an admin. Perhaps the PW is setting there as well. |
As I see you are working to "not" create openerp database per say, I think that is a good direction. Reason for doing so would be to put in TKL logos, branding things like that, but that would be overwritten right away anyway I feel. Just did a pull trying to have VER/REL/ARCh in 10-dependencies Will report with a new build soon. |
Not sure why I can't use now tried (seems to be building, but I hope it is correct) what am I missing here? |
Just did a successful build with everything seems to be working. Going to do another build to see if this is working again and not just a fluke. |
Cool. I'm was prepping such too. Seemes wierd in that I know you made some changes. root@tkldev products/tkl-odoo-dev# dir
|
It seems that everything works fine, however only after a reboot or a restart of the Postgres and odoo services. Looking at doing a init hook to restart the services By the way, the default odoo login is admin admin |
Cool. Is that set in 10-main ? I did not see where you set that? I am doing a build. Last one failed because I needed to uncomment REL and ARCH in my whtmltox wget. Lets see if it works now. I am working in dev-wip1 Should I do so before we try a Pull Request? |
My last build worked like a treat! I pushed my changes check out my branch and do a clean build and test the ISO install |
I tried three times, each one built and ISO installed. All services seemed to be working going to main website, asked to create a database! |
I am not sure you want to nest directories like that under products. I never have done that. I just create two directories odoo-1 and odoo2 under products. |
Good idea. I will get it flat. Have several folders out under products is all. my REV/VER/ARCH is not working right for wkhtmltox (will revert) in 10-dependencies(dev-wip1) ---- UPDATE will test again after kens-dev-wip1 which is running now (unnested) |
kens-dev-wip1 (my rc2 iso) Postgresql running at firstboot Second Boot But Running. I have a Snapshot saved. Will revert to "restart point" and see if I wait at "First Boot" (post passwords) I can get Odoo to come up by its own. May be I did not wait long enough. Would be interesting to have a "console" that said "when ODOO is ready" (complicated) |
Round 2 Odoo at First Boot Returns:
Odoo Second Boot
Why don't we just put a Reboot in the InitHook? Would this make sense? I realize better to just reboot the services. Looks great ALL THINGS considered. THANK YOU. |
I am working off of all SSD drives. My wait time was like 10 sec. During first boot did you see it stop and restart the services? |
Not visually anywhere. Would that be in the install screen? I will try again and see. Goes quick because I have a snapshot to "reboot" that is part of the Install Protocol. I will count to 10 and see whether I can get in after setting PW and taking in Updates (Updates could be part of the issue really - so I will skip them this next time) |
No visual reboot of services at first boot. (reordered EDIT for clarity) Still 500 Internal Server Error on First Boot Just tried to "stop/start" openerp-server in "running services" in Webmin. This time Prior was 500 error not 503 (Moved line below) Did Start Clean on Second Boot, no intervention. |
maybe I don't have the "restart" code yet, but I think I do. |
Updated Comment 2 above: |
in dev-wip1 I have a build. I won't install just now. If its in its in. Should we do a Pull Request into dev-wip1 ? |
What is your testing protocol? What steps do you take from build to installing to trying to test the app? Maybe I am missing something in your steps Mine is this I have a VM that is blank with a snapshot to the blank
|
Just did another test and I had no issues. |
I am basically doing the same except I don't see #11 anywhere. In TKLDEV I do If I do updates, perhaps it restarts all services then, however, no visual My system comes up to confconsole (blue screen) Great that it came up. |
Lets do a few Pulls (Pull Requests) test (this will merge with my ARCH update for 10-dependencie (whtmltox) dev-wip1 > dev Thoughts? |
@JedMeister I'll try the build with the said packages instead, also when using GIT to pull down software in TKLDev is there a TKL way of using the proxy for GIT? I know I can change the proxy.http/proxy.https config, did not know if there is a better way. If there is already a good way of doing this point me to the source :-) |
@DocCyblade - Sry for slow reply. TBH I never actually tested to see what works best; but according to my research git abides by the $http_proxy (and $https_proxy) system variables so something like this should do the trick:
|
I am not clear on the purpose of using http_proxy for Git in this situation. Is it not just for the build or is it for "post pulls". after ap install (ie in configurable inithooks)? |
@DocCyblade Let me know when you want any testing done. I am going to try to build a new TKLDEV. |
Landis, the proxy is only for the build process. Keeps you from requesting the GIT repos over and over (saves time and bandwidth) from building over and over Will start working on a base install once I get the kids in bed. Should be soon |
@l-arnold FWIW any TKL code that makes use of FAB/fab is almost certainly build related. Fab is one of the fundamental TKLDev tools. If you watch an appliance building you will see lots of lines that include & the TKLDev v14.0RC2 and the stable release are essentially the same. The only thing that changed was the installer ( |
@JedMeister FWIW: I found the below snippet of code here regarding GIT and TKLDev proxy.
I don't see however any GITHUB cached by checking
|
@JedMeister I also tried the following, does NOT seem to work.
What did work was, from the command line:
Not sure why during the build its not working I am heading to bed, will try some more in the AM or PM |
Ok. Start on comprehension. It would be great if I could use FAB but build full ISO's. I had understood I needed to go into CHROOT to do that (which I believe is how I broke my TKLDEV).... Will do some studying for sure. But back to the original subject. Sounds like the code would call the Proxy and "once built" stop calling the full Git on sequential builds. I assume my "make clean" then "make" (or "make clean && make") will by pass the proxy? Perhaps not. Assume the purpose of this is to use the same Git Pull for every iteration of the App Build so likely to not require the "make clean" but something like "make cloud" "make (etc etc)". All sounds good. Need to study the docs. |
@DocCyblade - great detective work! I had read that "HTTP_PROXY" (all caps) doesn't work with git but that you need to use "http_proxy" or "https_proxy" (no caps) instead. As I said I never actually tested/checked (as I probably should have) but took what I had read and used it. To elaborate on my understanding: However, seeing as you have found a technique that appears to work perhaps we can add that in the download conf script and remove it at the end? Or leave it there? Or something else? Also if we go that way then we probably should double check that it will work on a vanilla (unconfigured) TKLDev server (i.e. with the other bits of ~/.gitconf unconfigured - we could test by moving the fully configured file out and retry your steps above). @l-arnold fab is a component of TKLDev. when you issue the
Then you should be able to browse to your TKLDev IP; port 80 (i.e. http) in your web browser and see Odoo web UI! When you are done, exit the chroot and kill all processes running in your root.patched chroot:
After testing you can finish building with make:
Note though that any changes you made in the chroot will be lost. If you want to make changes they'll need to go in the overlay or conf scripts... The proxy is purely for caching while you are building. Usage of the proxy applies only while working within TKLDev. It means that you don't need to keep downloading the same files over and over everytime you |
Thank you for the instructions @JedMeister . I will see what comes of the FAB (ulous) Proxy work you and @DocCyblade are working on and give it all a spin. I will try the "fuser -k" command on my errant TKLDEV if it gives me troubles again as well. |
Nice pun! |
@JedMeister so I did some more testing, it seems it's not "caching" like we think it should. After reading (http://wildlyinaccurate.com/a-hackers-guide-to-git/) then my head exploding. I quickly picked up the bits of my head and figured the reason why. GIT is not pulling data that the proxy can understand and cache. So if we really want to "cache" GIT repos, we would need to create a custom script that does it for us. Not sure what the best way would be, but I think some script bash/python look something like this: The script would do the following
Some possible options the script could implement
May want to base the above on this Should I submit this as a feature request for FAB/TKLDev maybe a fab-git-clone or something that would keep cache? I am working a script now that will do this :-) |
@DocCyblade - your awesomeness never ceases to amaze me! 👍 Sounds like a great idea all round (dev of the tool, lodging as a feature request, etc). |
@JedMeister I have good ideas every so often, just happens the moon and stars aligned I guess! I will put in a feature request here soon. I started a shel script to do this. I used a template I found for shell scripting that I liked. I'll work on this as I have the time :-) |
@DocCyblade and @JedMeister Having done that the git-cache (and its subfolders) could be addressed by TKL builds just as common is addressed. Seems this functionality is actually already in place somehow as it is working with common. |
@l-arnold I am currently here (https://github.com/DocCyblade/tkl-odoo) working on building a basic install with no extras, the next thing to do would then be to test it. The idea is to start with a basic build, try and mimic as close as we can to the Odoo documentation, keeping service accounts and such in line with official documentation as well. If you want to start making a test list we can use for each release. I have outlined the released in steps or milestones (https://github.com/DocCyblade/tkl-odoo/milestones) So here is how I think this can best work.
We will release this build, release, test until we get what TKLDev find acceptable. I would like to open document testing and any decisions openly and in a systematic manner so that TKLDevs and Jeremy can see everything progress and why something was done the way it was etc. I have added you to the repo so I can assign you issues. Just don't edit any code via git hub on this repo. If you want to make changes, create a new branch, make changed then pull request. Going to move future discussions here (DocCyblade#1) |
Sounds generally good Ken. Would there not be sense in just making a "bare" branch in the current build (I do understand that is what is being built). Just working on the "module" list but it is a very "big one" that is a bit daunting. What would seem practical would be a way to "hook into the various repositories. I think Odoo / addons by nature are the "default". Ones like OCA are outside the Odoo repositories. I will focus on the ones "outside". I don't know that we can pull off the "optional" Module install but I do feel there would be great value in that approach. Could also apply to some other apps as well if a system were in place. This is the part where Odoo, given their corporate druthers, will complicate things for un-educated users and where the "open" source starts to fall out of focus. I would be curious if we could build some scripts that fire off the effect of each of the sections (and similar) in I will test and see if I can keep up with the testing matrix. Should not be a problem. Will endeavor to mimic aspects here as well. |
@DocCyblade - Love your work mate. IMO your process is one that I think all current and future TurnKey devs could benefit from (BTW IMO you are a TKL dev! & you too @l-arnold 😄) @l-arnold Optional module installs should be easy IMO. The third conf script that you have essentially does it from what I can see. Although there may be some base config which might need to be modified (your config is built to include that stuff - whereas a minimum base config may not). |
@JedMeister - From a fast hack point of view, so long as we can keep an "elaborate" and a "base" config generally aiming for the same folders and config setups my thought is that one way to do a "quick" jump to full build would be the following: Install Base to Cloud. That said, every folder, every configuration etc needs to be kept consistent. Needs to be consistent for V 15 etc for updates. I am a little worrried about this Repository drifting apart from Kens and the above not being funcitonal. |
btw, thanks for the smile and the "dev" moniker. 👍 😆 |
@l-arnold - My goal is two parts. Part one, make an entry level Odoo TK Build, Part two make it so that it can be customized to the end users liking after install. Part one, should get Odoo in the official repo, Part two is making it even better by allowing post install additions. I agree that whatever is done needs to stay that way. I would prefer TKL mirror that of install docs from the core dev at Odoo land. This way documentation from Odoo community would make sense in a TKL deployment as well. For me the whole TurnKey motto is, anyone that could download and ISO, install it can have a basic (fill in the blank) open source software. So that it's not confusing, point to the open softwares documentation and config files, etc are all similar. @JedMeister correct me if I am way off the reservation so to speak. My goal is to take the current code base, take it down to the frame, the start adding parts back on part by part, and testing as we go along, until we have an understanding of how it all works under the hood so we can later add to it. I plan on using as much if not all the code that is already written. Why re-invent the wheel? Instead, I am making a stock car 🚗 by taking apart a bus 🚌 , then putting it back together with the same parts and some new paint and creating limo 🚙 😄 Could not find a limo icon! |
@DocCyblade - totaly on the money IMO! 👍 FWIW here is the post that was already sitting in my browser...! 😄 That should work @l-arnold; although my preference would be for a script that could add the additional modules (or even better a group of scripts that users can manually run). If you keep in mind that the conf scripts in a TKLDev appliance build code repo are basically just install scripts that could be run on any Debian PC/server... Running those scripts should install the given software (in conjunction with the files that have been overlayed). In fact if you wanted to you should be able to copy across the overlay files and execute the conf script on Core and you should basically end up with the appliance. So moving the conf script for additional modules (conf.d/50_external_modules) out of the build code and into an optional post install script (e.g. Then once we have confconsole extended so that it supports additional config then they can be really easily added. Although as we are not clear at this stage what format the extended confconsole may take, so it's probably best to just make it a (some) simple bash script(s)... |
Keep me up on the testing and we should be good. I am quite skilled at stress tests. :smile |
Been doing a series of migrations. Brought working system up to dev-wip1 (beta 2). Thows over well etc. I would like to find out and document how to apply my SSL cert also to Webmin and Webshell. They don't seem to fall into my Apache way of doing things. Will look again today at the DEV branch to see why Openerp Service is not loading properly. |
Hey guys Just checking in. Been very busy here. I should be back in the game Friday night. I should have the base install compete, then start working on the next. Goal would be to make sure it works as designed. |
That's because they don't run on/behind Apache... They both run on their own (mini)servers although as of v14.0 they are both hidden behind (essentially proxied by) stunnel. So you'll need to do some reading (and probably trial and error) on how to configure stunnel to use a 3rd party CA cert. It would be quite good to have documented though! @DocCyblade - good work mate. I'm going to be away for the weekend so I'll be back on board Sunday night/Monday morning my time... |
@JedMeister and @DocCyblade |
I propose we move some of these conversations off of TRACKER and into Issues for tkl-nomadic-odoo as I am doing here.
Probably want to have @DocCyblade, @l-arnold and @JedMeister watching (yep) - updated. Also needed to bring JedMeister in as a Collaborator to get an @ to work.
The text was updated successfully, but these errors were encountered: